On Mon, 21 Apr 2008, Assaf Arkin wrote: > In 1.3 you can still filter test cases by class/package name, and that's > handled uniformly across all test frameworks using test.include/exclude. > > What you can't do is convince JUnit to select classes that are not JUnit > test cases, which was possible in 1.2, and a convenient hack before we had a > good test framework API. > > In 1.3 we cleaned that up. We now have an API for adding new test > framework, with some convenience methods for the Java frameworks, and even > three BDD frameworks using it (check out buildr/java/bdd_frameworks.rb). > > So that was a conscious decision to break the old behavior but move > developer to the new API. > > (Note: we still need to work on a uniform reporting mechanism for all the > different test frameworks)
Thanks Assaf! It seems that with the include / exclude + @RunWith fix, we can continue with the "convenient hack" of using the JUnit runner for running JDave specs. I had no idea that include and exclude were so easy to use, and hope to try them soon in practice. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ >
