6:36 a.m.
[
https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.sy...
]
Davy Herben edited comment on ARQ-567 at 7/18/13 7:35 AM:
----------------------------------------------------------
Hi, great work gentlemen. I've tested this on our project, where we have 1200
arquillian tests against a standalone glassfish 3.1, and using this extension easily cuts
our total build time in half! Very excited about this :)
I've encountered one issue though, which is killing the maven build. The build
correctly deploys the test archive only once, but it does not undeploy it after all
integration tests have run. This leaves the test archive deployed. On the next build, the
deployment fails because glassfish complains that the archive already exists. I've
been looking at a way to make arquillian provide the --force argument to the glassfish
deployment to force an override, but this does not seem to be possible with the current
adapter.
Any ideas on how to fix this? In case it matters: I have set up the maven failsafe plugin
to simply run all *ContainerIT tests, not to run a specific junit TestSuite.
was (Author: dherben):
Hi, great work gentlemen. I've tested this on our project, where we have 1200
arquillian tests against a standalone glassfish 3.1, and using this extension easily cuts
our total build time in half! Very excited about this :)
I've encountered one issue though, which is killing the maven build. The build
correctly deploys the test archive only once, but it does not undeploy it after all
integration tests have run. This leaves the test archive deployed. On the next build, the
deployment fails because glassfish complains that the archive already exists. I've
been looking at a way to make arquillian provide the --force argument to the glassfish
deployment to force an override, but this does not seem to be possible with the current
adapter.
Any ideas on how to fix this? In case it matters: I have set up the maven surefire plugin
to simply run all *ContainerIT tests, not to run a specific junit TestSuite.
Supporting Test Suites (@ArquillianSuite)
-----------------------------------------
Key: ARQ-567
URL: https://issues.jboss.org/browse/ARQ-567
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Mousavi Jahan Abadi S. M.
Currently, it is supported that JUnit test cases being run by Arquillian. This feature
request is request for supporting test suites too to be run by Arquillian too. Idea is
like:
@RunWith(ArquillianSuite.class)
@Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } )
public class AllTests{
@Deployment
public static JavaArchive createTestArchive(){
return ShrinkWrap.create(JavaArchive.class,"test.jar");
}
}
The advantages of above approach for users of Arquillian framework are:
- Test cases don't needed to be modified to have:
"(a)RunWith(Arquillian.class)" annotation. In other words, test cases will be pure
JUnit code, and no Arquillian code (results in less coding for end users).
- It is not necessary to include the static "@Deployment" methods in all test
cases any more, and only Test Suite need to define the archieving/deployment related
setting/definitions.
The advantage of above approach for framework itself is:
- From performance point-of-view, it becomes possible for Arquillian to deploy all test
cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one
test suite, instead of mulitple deploy/undeploy for each test case).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4644
days inactive
4644
days old
arquillian-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Davy Herben (JIRA)