[JBoss JIRA] Created: (ARQ-236) Should be able to configure the Container lifecycle based on the Test events
4:26 a.m.
Should be able to configure the Container lifecycle based on the Test events
----------------------------------------------------------------------------
Key: ARQ-236
URL: https://jira.jboss.org/browse/ARQ-236
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak Knutsen
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://jira.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.syst...
]
Thomas Diesler updated ARQ-236:
-------------------------------
Summary: Configure the Container lifecycle based on the Test events (was: Should be
able to configure the Container lifecycle based on the Test events)
Configure the Container lifecycle based on the Test events
----------------------------------------------------------
Key: ARQ-236
URL: https://jira.jboss.org/browse/ARQ-236
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak Knutsen
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 p.m.
New subject: [JBoss JIRA] Assigned: (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen reassigned ARQ-236:
---------------------------------
Assignee: Aslak Knutsen
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
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
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: http://www.atlassian.com/software/jira
4:55 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-236:
------------------------------
Component/s: Base Implementation
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
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: http://www.atlassian.com/software/jira
8:08 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Prabhat Jha commented on ARQ-236:
---------------------------------
This would be really awesome. I was just chatting with Martin Gencur on similar scenario
for ISPN-ARQ integration.
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
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: http://www.atlassian.com/software/jira
6:51 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
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: http://www.atlassian.com/software/jira
10:17 a.m.
New subject: [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Martin Gencur reassigned ARQ-236:
---------------------------------
Assignee: Martin Gencur (was: Aslak Knutsen)
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
9:13 a.m.
New subject: [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-236:
-----------------------------------
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
9:15 a.m.
New subject: [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
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
11:35 a.m.
New subject: [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen resolved ARQ-236.
-------------------------------
Fix Version/s: 1.0.0.Final
(was: 1.1.0.Beta1)
Resolution: Done
pushed upstream
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.0.0.Final
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
5:39 a.m.
New subject: [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-236:
------------------------------
Fix Version/s: 1.0.0.CR6
(was: 1.0.0.Final)
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.0.0.CR6
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
8:58 a.m.
New subject: [JBoss JIRA] (ARQ-236) Configure the Container lifecycle based on the Test events
[
https://issues.jboss.org/browse/ARQ-236?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-236.
-----------------------------
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.0.0.CR6
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
4559
days inactive
5039
days old
arquillian-issues@lists.jboss.org
11 comments
9 participants
participants (9)
-
Aslak Knutsen (Closed) (JIRA) -
Aslak Knutsen (Commented) (JIRA)
-
Aslak Knutsen (Issue Comment Edited) (JIRA)
-
Aslak Knutsen (JIRA)
-
Aslak Knutsen (Resolved) (JIRA)
-
Aslak Knutsen (Updated) (JIRA)
-
Martin Gencur (Assigned) (JIRA)
-
Prabhat Jha (JIRA)
-
Thomas Diesler (JIRA)