[arquillian-issues] [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
Aslak Knutsen (Issue Comment Edited) (JIRA)
jira-events at lists.jboss.org
Mon Nov 21 10:15:41 EST 2011
[ https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644361#comment-12644361 ]
Aslak Knutsen edited comment on ARQ-236 at 11/21/11 10:14 AM:
--------------------------------------------------------------
We're currently dropping method level and only support suite/class/manual level.
Method level is fairly easy to do manually by splitting up / extending the Test Methods into Test Classes.
was (Author: aslak):
We're currently dropping method level and only support suite and class level.
Method level is fairly easy to do manually by splitting up / extending the Test Methods into Test Classes.
> 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: Martin Gencur
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the arquillian-issues
mailing list