I was wondering what the preference would be for where to stick certain tests (specifically for testng || testng running junit tests ) for surefire? I can see that surefire-api has a good start for doing basic junit testing, would that be a good place to place testng tests as well?
The patches made so far in http://jira.codehaus.org/browse/MSUREFIRE-134apply to both maven-surefire-plugin as well as surefire-providers/surefire-testng . There are some existing un-used tests sitting over in the maven-surefire-plugin site that I'd like to update and patch in such a way that they are run with normal releases to ensure people notice breaking changes. Most of the changes in the surefire plugin are related to classpath issues, so the ultimate solution may require a mixture of the new plugin testing harness style + just executing a set of known pom configs such as what are in maven-surefire-plugin already. (that is to say, the tests are there but aren't linked to the main pom and so don't get executed unless it's intentional ) Any help at all in a general direction of where to put code so that my patching efforts aren't in vain/not wanted would be greatly appreciated. -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
