[JBoss JIRA] Created: (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
2:54 a.m.
Arquillian must scale to a high number of full-layer integration tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons. This should be tested.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
[
https://issues.jboss.org/browse/ARQ-615?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet updated ARQ-615:
---------------------------------
Description:
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and the
IDE (without forcing the users to jump through many hoops to set up his IDE just right for
arquillian).
was:
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons. This should be tested.
Arquillian must scale to a high number of full-layer integration
tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and
the IDE (without forcing the users to jump through many hoops to set up his IDE just right
for arquillian).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
[
https://issues.jboss.org/browse/ARQ-615?page=com.atlassian.jira.plugin.sy...
]
Andrew Rubinger commented on ARQ-615:
-------------------------------------
"High difficulty setting up a @Deployment method" seems a separate concern to
this issue. But note that SHRINKWRAP-325 is now upstream.
Arquillian must scale to a high number of full-layer integration
tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and
the IDE (without forcing the users to jump through many hoops to set up his IDE just right
for arquillian).
--
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
10:26 a.m.
New subject: [JBoss JIRA] (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
[
https://issues.jboss.org/browse/ARQ-615?page=com.atlassian.jira.plugin.sy...
]
Andrew Rubinger commented on ARQ-615:
-------------------------------------
Also it looks like ARQ-197 more accurately describes this issue; perhaps this can be
closed as duplicate and my comment above moved there?
Arquillian must scale to a high number of full-layer integration
tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and
the IDE (without forcing the users to jump through many hoops to set up his IDE just right
for arquillian).
--
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
10:26 a.m.
New subject: [JBoss JIRA] (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
[
https://issues.jboss.org/browse/ARQ-615?page=com.atlassian.jira.plugin.sy...
]
Andrew Rubinger commented on ARQ-615:
-------------------------------------
This issue likely ties into discussions I've had w/ Aslak and Dan about decoupling
handlers (ie. Deployment) from events (ie. @BeforeClass). From a base level I think what
we should be doing is:
1) Re-evaluating the event model
2) Determine how events/handlers should be decoupled and then linked back together
(they're already mostly decoupled; but the re-linking is static ATM)
3) Determine if we can apply this to ARQ 1.x.y series (ie. no API changes)
4) If not, apply this to 2.x
Arquillian must scale to a high number of full-layer integration
tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and
the IDE (without forcing the users to jump through many hoops to set up his IDE just right
for arquillian).
--
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
10:34 a.m.
New subject: [JBoss JIRA] (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
[
https://issues.jboss.org/browse/ARQ-615?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet resolved ARQ-615.
----------------------------------
Resolution: Duplicate Issue
Duplicates ARQ-197 and SHRINKWRAP-325 and ARQ-629
Arquillian must scale to a high number of full-layer integration
tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and
the IDE (without forcing the users to jump through many hoops to set up his IDE just right
for arquillian).
--
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
7:23 a.m.
New subject: [JBoss JIRA] (ARQ-615) Arquillian must scale to a high number of full-layer integration tests
[
https://issues.jboss.org/browse/ARQ-615?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-615.
-----------------------------
duplicate
Arquillian must scale to a high number of full-layer integration
tests
----------------------------------------------------------------------
Key: ARQ-615
URL: https://issues.jboss.org/browse/ARQ-615
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Geoffrey De Smet
Priority: Critical
A full-layer integration test is an arquillian test which deploys the entire war of a
webapp (for example guvnor-webapp) and then runs a higher number of test classes and test
methods on it.
Currently arquillian doesn't scale out to that. For different reasons.
The main reason is ARQ-197: every test case starts the container again and after a while
tomcat6-managed goes out of memory.
But there are other reasons, such as high difficulty setting up an @Deployment method.
SHRINKWRAP-325 is trying to fix that later.
This should be tested and any solutions should work both from the mvn command line and
the IDE (without forcing the users to jump through many hoops to set up his IDE just right
for arquillian).
--
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
4638
days inactive
4852
days old
arquillian-issues@lists.jboss.org
6 comments
4 participants
participants (4)
-
Andrew Rubinger (Commented) (JIRA) -
Aslak Knutsen (JIRA)
-
Geoffrey De Smet (JIRA)
-
Geoffrey De Smet (Resolved) (JIRA)