]
Aslak Knutsen updated ARQ-236:
------------------------------
Fix Version/s: 1.1.0.Beta1
Configure the Container lifecycle based on the Test events
----------------------------------------------------------
Key: ARQ-236
URL:
https://issues.jboss.org/browse/ARQ-236
Project: Arquillian
Issue Type: Feature Request
Components: Base Implementation
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.1.0.Beta1
A user should be able to customize how he wants the Container to be controlled.
The default behavior is:
@BeforeSuite -> container.start()
@BeforeClass -> container.deploy()
@AfterClass -> container.undeploy()
@AfterSuite -> container.stop()
Other scenarios are:
- Restart server pr test class
@BeforeClass -> container.start()
@BeforeClass -> container.deploy()
@AfterClass -> container.undeploy()
@AfterClass -> container.stop()
- Redeploy pr test method
@BeforeSuite -> container.start()
@Before -> container.deploy()
@After -> container.undeploy()
@AfterSuite -> container.stop()
- Restart pr test method
@Before -> container.start()
@Before -> container.deploy()
@After -> container.undeploy()
@After -> container.stop()
This could be done by adding a Engine configuration option
e.g.:
engine/containerLifeCycle PrSuite|PrClass|PrMethod
this option would map to different ContextAppenders in the background that does the
setup/ordering.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: