One of the things I have found difficult with the transition to JUnit4 is a couple of our test cases where we perform the same test on a range of test data. While I admit this is not strict unit testing that JUnit was designed for it is something that we could pull of in JUnit3 pretty well.
I found this excellent thread here: - http://radio.javaranch.com/lasse/2006/07/27/1154024535662.html But even it runs dry; it looks like a couple people in the thread had similar issues and were not able to explain them. I am thinking of classes like DOMParserTestSuite; which create a Test for each file in a folder; performing the same kind of tests on each. Right now this shows up as a series of "Unrooted Tests" when I run it in eclipse. Does anyone have any feedback on this; or is this a style of testing that we should give up on? Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
