[
https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s...
]
Jakub Senko edited comment on AS7-4065 at 8/2/12 1:27 PM:
----------------------------------------------------------
I have found an issue which results in different tests being run when running a single
test using failsafe plugin instead of surefire.
It is caused by an issue described here:
http://jira.codehaus.org/browse/SUREFIRE-856
*Description*
If you run a specific integration test using CLI property, surefire will ignore
<includes> patterns.
However, failsafe will not, which causes only tests defined in <includes> being
considered, so failsafe will only run a subset
of tests ran by surefire.
*Reproduction steps*
Using upstream version (uses surefire plugin for IT testing) and executing following
command in testsuite/integration:
{code}mvn clean verify
-Dtest=org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
\
-Dts.clust -Dts.noSmoke{code}
the specified test will run.
Using my jboss-as fork (
http://github.com/jsenko/jboss-as) which uses failsafe pluging for
IT testing, executing following command in the same directory:
{code}mvn clean verify
-Dit.test=org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
\
-Dts.clust -Dts.noSmoke{code}
will not execute any tests.
was (Author: jsenko):
I have found an issue which results in different tests being run when running a single
test using failsafe plugin instead of surefire.
It is caused by an issue described here:
http://jira.codehaus.org/browse/SUREFIRE-856
*Description*
If you run a specific integration test using CLI property, surefire will ignore
<includes> patterns.
However, failsafe will not, which causes only tests defined in <includes> being
considered, so failsafe will only run a subset
of tests ran by surefire.
*Reproduction steps*
Using upstream version (uses surefire plugin for IT testing) and executing following
command in testsuite/integration:
{code}mvn clean verify
-Dtest=org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
-Dts.clust -Dts.noSmoke{code}
the specified test will run.
Using my jboss-as fork (
http://github.com/jsenko/jboss-as) which uses failsafe pluging for
IT testing, executing following command in the same directory:
{code}mvn clean verify
-Dit.test=org.jboss.as.test.clustering.extended.ejb2.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
-Dts.clust -Dts.noSmoke{code}
will not execute any tests.
TS: Migrate from Surefire to Failsafe maven plugin.
---------------------------------------------------
Key: AS7-4065
URL:
https://issues.jboss.org/browse/AS7-4065
Project: Application Server 7
Issue Type: Enhancement
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Jakub Senko
Fix For: 7.2.0.Alpha1
Surefire aims at unit testing.
Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify.
That not only moves test execution to the correct phase, but also brings possibility to
test several issues present in the testsuite - like skipping successive Surefire
executions in a single module if former fails (not affected by -fae).
--
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