Proposal:
1) Switch to JUnit 4.4 or above on trunk (volunter for that?).
2) Create some base class to be extended by every GeoTools test
(in JUnit 4 we do not need to extends TestCase anymore).
3) In the above base case, put the following constants:
protected static final extensive = Boolean.getBoolean("a system property");
protected static final online = Boolean.getBoolean("a system property");
// maybe some others
4) Progressively abandon the current policy we have for extensive
and online test, to be replaced by the new "assumptions" feature
of JUnit 4.4:
http://junit.sourceforge.net/doc/ReleaseNotes4.4.html#assumptions
Example:
@Test
public void myLongTest() {
assumeTrue(extensive);
doMyLongTest...
}
If the "extensive" boolean value is false, the whole test is marked as
passed. This has the advantage of allowing finer grain control than
marking a whole file as "OnlineTest" and to show explicitly in the JUnit
report which tests where passed (currently nothing tell us that some tests
where passed).
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
