The Maven team is pleased to announce the release of the Maven Surefire Plugin, version 2.7.2
This release includes the maven-surefire-plugin, which executes the unit tests of an application, the maven-surefire-report-plugin, which parses surefire/failsafe test results and renders them to DOXIA creating the web interface version of the test results, as well as the maven-failsafe-plugin, which executes the integration tests of an application. Highlights of this release: http://jira.codehaus.org/browse/SUREFIRE-257 is fixed, which is the third highest voted maven issue ever. It's now possible to consolidate surefire and failsafe reports due to http://jira.codehaus.org/browse/SUREFIRE-570 being fixed. **** Note to JUnit4 users upgrading: Due to SUREFIRE-482 users upgrading to surefire 2.7.2 from <2.7 may see some (incorrectly defined) tests not being run any more. This should be verified by running mvn -Dsurefire.junit4.upgradecheck=true install at least once (this can be run multiple times until you have fixed all issues) http://maven.apache.org/plugins/maven-surefire-plugin/ You should specify the version in your project's plugin configuration: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.7.2</version> </plugin> Release Notes - Maven Surefire - Version 2.7.2 ** Bug * [SUREFIRE-257] - surefire-report reruns tests * [SUREFIRE-260] - Detail display doesn't work if there are tests with the same name * [SUREFIRE-319] - <skip>true</skip> cannot be overridden using mvn -Dmaven.test.skip=false test * [SUREFIRE-424] - A class providing JUnit's suite() method need not itself implement Test. But Surefire ignores the suite if it doesn't. * [SUREFIRE-468] - When tests timeout, report files on disk are incorrect * [SUREFIRE-480] - Improper TestCase classes incorrectly reported as a failure of the TestSuite class * [SUREFIRE-498] - POJO tests have only partially implemented fixture support * [SUREFIRE-500] - puzzling NoClassDefFoundError instead of meaningfull stacktrace * [SUREFIRE-510] - surefire.test.class.path is not set when forkMode is always * [SUREFIRE-515] - Executes nested classes that are not tests * [SUREFIRE-516] - Definition of multiple Suite-Files not working * [SUREFIRE-519] - junit-dep 4.4+ isn't detected - transitive dependency to JUnit-3.x causes POJO-test treatment * [SUREFIRE-542] - JUnit 4.4 tests skipped for a failed assumption are not reported as "Skipped" * [SUREFIRE-548] - System properties not inherited * [SUREFIRE-560] - tests with @Ignore are treated as "unsuccessful" * [SUREFIRE-562] - Exorbitant long site-build since surefire 2.4 * [SUREFIRE-568] - Fork mode of "pertest" or "always" does not fork per test or always * [SUREFIRE-570] - Empty surefire reports when a multi-module project is ran with multiple report directories in surefire-report configuration * [SUREFIRE-625] - Testclass which fails during launch claims to have no tests * [SUREFIRE-677] - Improve param documentation * [SUREFIRE-679] - [regression] TestNG suite no longer succeeds, with error "testSetStarting called twice" * [SUREFIRE-680] - Printout Running TestSuite twice times * [SUREFIRE-682] - <skipTests> cannot be overridden by commandline param * [SUREFIRE-685] - Cannot pass multiple comma-separated includes * [SUREFIRE-687] - JunitCore runs classes that are not tests ** Improvement * [SUREFIRE-645] - Meaningful message when test has no runnable methods * [SUREFIRE-675] - perCoreThreadCount/useUnlimitedThreads param should be boolean * [SUREFIRE-676] - useSystemClassLoader should have default-value declared through annotation * [SUREFIRE-678] - Fixes to the upgrade check doc * [SUREFIRE-684] - Avoid duplicate code in AbstractSurefireMojo ** Test * [SUREFIRE-546] - test case for @Test(threadPoolSize) Enjoy, -The Maven team --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
