I think JUnit 4 is the way to, *after* we ship 1.3. Though I don't mind checking out TestNG too for that release.
Martijn On 5/29/07, Timo Rantalaiho <[EMAIL PROTECTED]> wrote:
On Tue, 29 May 2007, Martijn Dashorst wrote: > Also, please note that when we move to JDK 1.5, we can put this > discussion to rest, as we can annotate our tests to not run (JUnit > 4.x). They will then be reported as skipped tests and not end up in > oblivion. TestNG is also a possibility, but I overheard that the maven > surefire plugin is not up to par. With JDK 1.4, you can separate different kinds of tests with a naming convention, and then run name-based, dynamic suites with DirectorySuiteBuilder from JUnit extensions. We have used this approach a lot. Then there would be one suite that would be run by default (this can be set in surefire settings) and that should always pass 100 %, and another suite for developers, which would also include "TestBug" or some such suffix that would be used for temporarily failing tests. This is also handy for separating slow-running tests from quick tests (though as much as possible should be covered by quick tests anyway). JUnit 4 / TestNG test groups can be used to do this a lot more elegantly. - Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ >
-- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
