Map client events 1 to 1 with container events
----------------------------------------------
Key: ARQ-350
URL:
https://issues.jboss.org/browse/ARQ-350
Project: Arquillian
Issue Type: Feature Request
Components: Base Implementation, Test Protocol SPIs and Implementation
Reporter: Aslak Knutsen
We should redo how the test execution lifecycles happen. In the current impl the flow is:
Client(BeforSuite, BeforeClass, Before) -> Container(BeforSuite, BeforeClass, Before,
Test, After, AfterClass, AfterSuite) -> Client(After, AfterClass, AfterSuite)
We should map these 1 to 1 with the incontainer execution and keep the test instance alive
between the calls.
Client(BeforeClass) -> Container(BeforeClass)
Client(Before) -> Container(Before)
..
This way the execution is closer to how it normally would be, and extensions can interact
with the Container/Environment or Client in the appropriate lifecycles more naturally.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira