Author: krosenvold
Date: Tue Dec 21 17:44:13 2010
New Revision: 1051580
URL: http://svn.apache.org/viewvc?rev=1051580&view=rev
Log:
[SUREFIRE-670] Added docs about upgradecheck flag
Modified:
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm
Modified:
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm?rev=1051580&r1=1051579&r2=1051580&view=diff
==============================================================================
---
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm
(original)
+++
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/junit.apt.vm
Tue Dec 21 17:44:13 2010
@@ -32,6 +32,18 @@ Using JUnit
Surefire supports three different generations of JUnit: JUnit 3.8.x, JUnit
4.x (serial provider) and JUnit 4.7 (junit-core provider
with parallel support). The provider is selected based on the JUnit version
in your project and the configuration parameters (for parallel).
+* Upgrade check for JUnit 4.x
+
+ As of version 2.7, the algorithm for choosing which tests to change
+ has run. Form 2.7 and on only run valid JUnit tests for all versions of
JUnit, where older versions
+ would run invalid tests that satisfied a naming convention.
+
+ When upgrading from a version < 2.7 to a newer version, the build can be run
with
+ the flag -Dsurefire.junit4.upgradecheck which will notify you of any tests
that
+ will not be run any more (and the build fails). This is only meant to be
used as a tool
+ when upgrading to check that all your tests will be run. It is a transitional
+ feature that will be removed in a future version of surefire.
+
* How is the provider chosen ?
If nothing is configured, surefire detects which junit version to use by
the following algorithm:
