Thanks, it took some poking around to figure it out, but this is what
I ended up doing and it works:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<excludes>
<exclude>**/Test*.java, **/*Test.java, **/*Tests.java,
**/*TestCase.java</exclude>
</excludes>
<includes>
<include>**/FullTestSuite.java</include>
</includes>
</configuration>
</plugin>
</plugins>
</build>
On 11/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/9/06, Paul Barry <[EMAIL PROTECTED]> wrote:
> That might work, but I think what I'd rather do is just create a one
> TestSuite that does the setup beforehand, then run the tests.
Are you using JUnit? It sounds like a TestSetup class would be useful here.
> I have
> noticed that maven seems to run the tests based on a naming
> convention, *Test.java gets run, but *Tests.java don't. Can I
> override this somehow?
See:
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#includes
The default includes are **/Test*.java **/*Test.java **/*TestCase.java
You can override this (and excludes) in the plugin configuration.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
