-
Feature Request
-
Resolution: Done
-
Major
-
None
-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:
...
(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
...
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.
