Hi,
the maven plugin for TestedBy is now available at
https://testedby.googlecode.com/svn/plugins/maven/trunk .
Here is an example of configuration that can be added to a project
pom.xml we want to use TestedBy on:
<plugin>
<groupId>it.javalinux.testedby.plugins</groupId>
<artifactId>maven-testedby-plugin</artifactId>
<version>@pom.version@</version>
<configuration>
<verbose>true</verbose>
<staleMillis>100</staleMillis>
<runnerClass>it.javalinux.testedby.runner.impl.JunitTestRunner</runnerClass>
</configuration>
<executions>
<execution>
<phase>process-test-classes</phase>
<goals>
<goal>testedby</goal>
</goals>
</execution>
</executions>
</plugin>
Of course the plugin is meant to be run once all the classes (including
tests) have been compiled; this means that you either need to run it at
the right time with a direct invocation ('mvn testedby:testedby') or
bind it to the process-test-classes as show in the example above (and
run maven till that phase, 'mvn process-test-classes').
Take a look at the it.javalinux.testedby.plugins.TestedByMojo for all
the available configuration parameters (includes, excludes, testedby
runner, etc.).
The TestedBy Maven Plugin sub-project has unit tests as well as an
integration test structure for for using the Maven Invoker Plugin to
call the TestedBy plugin itself and verify its results through BeanShell
scripts (see src/test/resources/test-embedded).
If you want to play with adding additional integration tests reproducing
complex usecases (the current one simply run the plugin from a clean
test project), that would be really appreciated.
Cheers
Alessio