[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ] Jakub Senko reassigned AS7-4065: -------------------------------- Assignee: Jakub Senko (was: Ondrej Zizka) -- 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

[ 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. -- 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

[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ] Jakub Senko commented on AS7-4065: ---------------------------------- In order to use failsafe, it has to be specified in jboss-parent-pom. Failsafe has been added to the version 10-SNAPSHOT, but it is not available in version 9, which is currently in use. How do i request a release of a new version? Or is there some workaround? -- 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