52892d03bf
- Added new <code>clover:test-single</code> goal to execute a single test case and to view the test coverage result directly using the Clover Swing viewer. This is useful if you wish to quickly see the action that a single unit test has on the code it tests. git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@115838 13f79535-47bb-0310-9956-ffa450edef68
108 lines
3.6 KiB
XML
108 lines
3.6 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
|
<!--
|
|
/*
|
|
* Copyright 2001-2004 The Apache Software Foundation.
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
-->
|
|
|
|
<document>
|
|
<properties>
|
|
<title>Maven Clover plugin goals</title>
|
|
<author email="dion@apache.org">dIon Gillard</author>
|
|
<author email="vmassol@apache.org">Vincent Massol</author>
|
|
</properties>
|
|
<body>
|
|
<section name="Registering a Clover report">
|
|
<p>
|
|
The typical way to use the Clover plugin is by registering a Clover
|
|
report in your <code>project.xml</code>:
|
|
</p>
|
|
<source><![CDATA[
|
|
<reports>
|
|
<report>maven-clover-plugin</report>
|
|
[...]
|
|
</reports>
|
|
]]></source>
|
|
</section>
|
|
<goals>
|
|
<goal>
|
|
<name>clover</name>
|
|
<description>
|
|
This is the default goal. It compiles the project code with Clover,
|
|
executes the unit tests and generate Clover reports by calling the
|
|
<code>clover:report</code> goal.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:test</name>
|
|
<description>
|
|
Compiles the project code with Clover and executes the unit tests.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:test-single</name>
|
|
<description>
|
|
Execute a single unit test and view the test coverage result directly
|
|
using the Clover Swing viewer. This is useful if you wish to quickly
|
|
see the action that a single unit test has on the code it tests.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:report</name>
|
|
<description>
|
|
Generate Clover test coverage reports with Clover. There are 3
|
|
possible reports: HTML, XML or Swing. Whether a report is generated
|
|
is controller by the <code>maven.clover.report.[report name]</code>
|
|
<a href="properties.html">properties</a>. The generated reports show
|
|
exactly what lines of your code were exercised by your tests.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:xml-report</name>
|
|
<description>
|
|
Generate an XML test coverage report with Clover.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:html-report</name>
|
|
<description>
|
|
Generate an HTML test coverage report with Clover.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:swing-report</name>
|
|
<description>
|
|
Generate a Swing test coverage report with Clover.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:on</name>
|
|
<description>
|
|
Activates Clover, which means that any other plugin calling the Ant
|
|
<code>javac</code> task will find its code compiled with Clover. This
|
|
is useful for example to Clover Cactus tests:
|
|
<code>maven clover:on cactus</code>.
|
|
</description>
|
|
</goal>
|
|
<goal>
|
|
<name>clover:off</name>
|
|
<description>
|
|
Deactivates Clover, resetting back the normal <code>javac</code> compiler.
|
|
</description>
|
|
</goal>
|
|
</goals>
|
|
</body>
|
|
</document> |