[jbosstools-issues] [JBoss JIRA] (JBIDE-13289) Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup
Snjezana Peco (JIRA)
jira-events at lists.jboss.org
Wed Dec 12 15:56:17 EST 2012
[ https://issues.jboss.org/browse/JBIDE-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Snjezana Peco reassigned JBIDE-13289:
-------------------------------------
Assignee: Snjezana Peco
> Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-13289
> URL: https://issues.jboss.org/browse/JBIDE-13289
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Lukáš Fryč
> Assignee: Snjezana Peco
>
> {{-Darquillian.debug=true}} allow more insight into test lifecycle and drastically improves debugging experience by outputting call tree of Arquillian event system.
> There is sample call tree for debugging Warp client-side [full tree|https://gist.github.com/4270739]:
> {code}
> ...
> (E) Before
> (I) TestContextHandler.createSuiteContext
> (I) TestContextHandler.createClassContext
> (E) TestClass
> (I) TestContextHandler.createTestContext
> (I) ContainerEventController.createBeforeContext
> (O) DroneConfigurator.configureDrone
> (O) TestInstanceEnricher.enrich
> (E) BeforeEnrichment
> (E) RequireProxy
> (O) ProxyObserver.requireProxy
> (E) StartProxy
> (O) ProxyObserver.startProxy
> (E) AfterEnrichment
> (O) ClientBeforeAfterLifecycleEventExecuter.on
> (E) Test
> (I) TestContextHandler.createSuiteContext
> ...
> {code}
> Similarly for container.
> ----
> The problem with debugging is that people need to setup VM arguments in Container Configuration
> and then setup JUnit/TestNG VM arguments for each *executed test specifically*.
> ----
> This button switch in toolbar should allow to add {{-Darquillian.debug=true}} to executed test (either JUnit or TestNG) and also into container configuration.
--
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 jbosstools-issues
mailing list