[arquillian-issues] [JBoss JIRA] (ARQGRA-213) print contextpath and option to sleep after starting the @Deployment

Lukáš Fryč (JIRA) jira-events at lists.jboss.org
Wed Dec 12 04:56:17 EST 2012


    [ https://issues.jboss.org/browse/ARQGRA-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740836#comment-12740836 ] 

Lukáš Fryč commented on ARQGRA-213:
-----------------------------------

[~kpiwko], the development mode leaving deployment deployed after test could be actually part of Drone, wdyt?
                
> print contextpath and option to sleep after starting the @Deployment
> --------------------------------------------------------------------
>
>                 Key: ARQGRA-213
>                 URL: https://issues.jboss.org/browse/ARQGRA-213
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Mark Struberg
>            Assignee: Lukáš Fryč
>             Fix For: 2.0.0.Alpha3
>
>
> Most graphene unit test have a @Deployment section and something similar to the following:
> {code}
>     @ArquillianResource
>     private URL contextPath;
> {code}
> When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information.
> Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the arquillian-issues mailing list