Re: [rmf-dev] Help wanted: Best practices for Hudson test setup

[Mark Brörkens <mark.broerkens@xxxxxxxxx>]

Hi Michael, hi Lukas,

the selection of test cases is configured in the pom.xml. Currently all files with the naming pattern **/All*Tests.class are executed:
<plugin>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-surefire-plugin</artifactId>
	<version>${tycho-version}</version>
	<configuration>
		<includes>
			<include>**/All*Tests.class</include>
		</includes>
		<useUIHarness>false</useUIHarness>
		<useUIThread>false</useUIThread>
		<argLine>${test.vmargs}</argLine>
	</configuration>
</plugin>

You can get rid of the test suits if you change the include pattern to e.g. **/*Tests.class.
In order to exclude abstract test cases you can use the excludes configuration.

For more information about how to configure tests that are executed in tycho-maven please see: 
http://www.eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html

Regards

Mark


Am 12.04.2012 um 12:34 schrieb Michael Jastram:

> Hello all,
> 
> As Lukas announced, we now have test running on Hudson.  However, we
> currently have to hard code the test suites.  This in turn means that
> the test suites have to be maintained.
> 
> Wouldn't it be nicer if Hudson would find the tests by itself, and we
> would get rid of the suites altogether?
> 
> Does anybody know what the best practices are?  Is there a reason for
> keeping the suites around?
> 
> Thanks,
> 
> - Michael & Lukas
> 
> -- 
> Michael Jastram (http://www.jastram.de, +49 (162) 274 83 94)
> Geschäftsführer, Formal Mind GmbH (http://formalmind.com)
> Wissenschaftler, Heinrich Heine Universität Düsseldorf (http://www.stups.uni-duesseldorf.de)
> 1. Vorsitzender, rheinjug e.V. (http://www.rheinjug.de)
> 
> 
> _______________________________________________
> rmf-dev mailing list
> rmf-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/rmf-dev