Author: jaikiran
Date: Sat Jun 2 03:56:04 2018
New Revision: 1832721
URL: http://svn.apache.org/viewvc?rev=1832721&view=rev
Log:
junitlauncher task, in the current released version, already allows
"includeEngines" and "excludeEngines" attribute for test definition; update the
documentation to reflect that
Modified:
ant/site/ant/production/manual/Tasks/junitlauncher.html
Modified: ant/site/ant/production/manual/Tasks/junitlauncher.html
URL:
http://svn.apache.org/viewvc/ant/site/ant/production/manual/Tasks/junitlauncher.html?rev=1832721&r1=1832720&r2=1832721&view=diff
==============================================================================
--- ant/site/ant/production/manual/Tasks/junitlauncher.html (original)
+++ ant/site/ant/production/manual/Tasks/junitlauncher.html Sat Jun 2 03:56:04
2018
@@ -118,9 +118,9 @@
<h3>Parameters</h3>
<table class="attr">
<tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required</th>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ <th scope="col">Required</th>
</tr>
<tr>
<td>haltOnFailure</td>
@@ -211,9 +211,9 @@
</p>
<table class="attr">
<tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required</th>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ <th scope="col">Required</th>
</tr>
<tr>
<td>type</td>
@@ -285,9 +285,9 @@
<table class="attr">
<tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required</th>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ <th scope="col">Required</th>
</tr>
<tr>
<td>name</td>
@@ -330,6 +330,28 @@
is <strong>not</strong> set</a>.</td>
<td>No</td>
</tr>
+ <tr>
+ <td>includeEngines</td>
+ <td>A comma separated set of test engine ids. If specified, only these
test engine(s)
+ will be used for running the tests.
+ <br/>
+ For example: <code>includeEngines="junit-jupiter"</code> will only
use the Jupiter
+ test engine for execution of the tests and will ignore any other
engines that might
+ have been found in the classpath.
+ </td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>excludeEngines</td>
+ <td>A comma separated set of test engine ids. If specified, these test
engine(s)
+ will be excluded when running the tests.
+ <br/>
+ For example: <code>excludeEngines="junit-vintage"</code> will
exclude the vintage
+ test engine during execution of the tests and will use any other
engines that might
+ have been found in the classpath.
+ </td>
+ <td>No</td>
+ </tr>
</table>
<p>
@@ -349,9 +371,9 @@
<table class="attr">
<tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required</th>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ <th scope="col">Required</th>
</tr>
<tr>
<td>haltOnFailure</td>
@@ -383,6 +405,28 @@
is <strong>not</strong> set</a>.</td>
<td>No</td>
</tr>
+ <tr>
+ <td>includeEngines</td>
+ <td>A comma separated set of test engine ids. If specified, only these
test engine(s)
+ will be used for running the tests.
+ <br/>
+ For example: <code>includeEngines="junit-jupiter"</code> will only
use the Jupiter
+ test engine for execution of the tests and will ignore any other
engines that might
+ have been found in the classpath.
+ </td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>excludeEngines</td>
+ <td>A comma separated set of test engine ids. If specified, these test
engine(s)
+ will be excluded when running the tests.
+ <br/>
+ For example: <code>excludeEngines="junit-vintage"</code> will
exclude the vintage
+ test engine during execution of the tests and will use any other
engines that might
+ have been found in the classpath.
+ </td>
+ <td>No</td>
+ </tr>
</table>
<p>
@@ -392,6 +436,10 @@
<h3>Examples</h3>
+<p>
+ Launch the JUnit 5 platform to run the <samp>org.myapp.SimpleTest</samp>
test
+</p>
+
<pre>
<path id="test.classpath">
...
@@ -403,7 +451,9 @@
</junitlauncher></pre>
<p>
- Launches the JUnit 5 platform to run the <samp>org.myapp.SimpleTest</samp>
test
+ Launch the JUnit 5 platform to run the <samp>org.myapp.SimpleTest</samp>
and
+ the <samp>org.myapp.AnotherTest</samp> tests. The build process will be
stopped if any test, in
+ the <samp>org.myapp.SimpleTest</samp>, fails.
</p>
<pre>
@@ -415,9 +465,8 @@
</pre>
<p>
- Launches the JUnit 5 platform to run the <samp>org.myapp.SimpleTest</samp>
and
- the <samp>org.myapp.AnotherTest</samp> tests. The build process will be
stopped if any test, in
- the <samp>org.myapp.SimpleTest</samp>, fails.
+ Launch the JUnit 5 platform to run only the <samp>testFoo</samp> and
<samp>testBar</samp>
+ methods of the <samp>org.myapp.SimpleTest</samp> test class.
</p>
<pre>
@@ -427,8 +476,10 @@
</junitlauncher></pre>
<p>
- Launches the JUnit 5 platform to run only the <samp>testFoo</samp> and
<samp>testBar</samp>
- methods of the <samp>org.myapp.SimpleTest</samp> test class.
+ Select any <samp>.class</samp> files that match
+ the <samp>org/example/**/tests/**/</samp> <code>fileset</code> filter,
under
+ the <samp>${build.classes.dir}</samp> and passes those classes to the
JUnit 5 platform for
+ execution as tests.
</p>
<pre>
@@ -443,10 +494,14 @@
</junitlauncher></pre>
<p>
- Selects any <samp>.class</samp> files that match
+ Select any <samp>.class</samp> files that match
the <samp>org/example/**/tests/**/</samp> <code>fileset</code> filter,
under
- the <samp>${build.classes.dir}</samp> and passes those classes to the
JUnit 5 platform for
- execution as tests.
+ the <samp>${build.classes.dir}</samp> and pass those classes to the JUnit
5 platform for
+ execution as tests. Test results will be written out to the
<samp>${output.dir}</samp> by
+ the <q>legacy-xml</q> and <q>legacy-plain</q> formatters, in separate
files. Furthermore, both
+ the <q>legacy-xml</q> and the <q>legacy-plain</q> listeners, above, are
configured to receive
+ the standard output content generated by the tests. The <q>legacy-xml</q>
listener is configured
+ to receive standard error content as well.
</p>
<pre>
@@ -461,16 +516,6 @@
<listener type="legacy-plain" sendSysOut="true" />
</testclasses>
</junitlauncher></pre>
-<p>
- Selects any <samp>.class</samp> files that match
- the <samp>org/example/**/tests/**/</samp> <code>fileset</code> filter,
under
- the <samp>${build.classes.dir}</samp> and passes those classes to the
JUnit 5 platform for
- execution as tests. Test results will be written out to the
<samp>${output.dir}</samp> by
- the <q>legacy-xml</q> and <q>legacy-plain</q> formatters, in separate
files. Furthermore, both
- the <q>legacy-xml</q> and the <q>legacy-plain</q> listeners, above, are
configured to receive
- the standard output content generated by the tests. The <q>legacy-xml</q>
listener is
- configured to receive standard error content as well.
-</p>
</body>
</html>
