On 31/10/2006, at 6:42 PM, Jason van Zyl wrote:
On 30 Oct 06, at 2:24 PM 30 Oct 06, Brett Porter wrote:
This is really a question for the users list, but since we're here
these are probably the alternatives you have:
- use profiles to distringuish which tests run when (by
reconfiguring the surefire plugin)
- using testng with groups to categorise the tests
All good except for system properties Might be running in the
embedder for more then one version at a time.
That's why most IDEs, and surefire by default, fork a JVM for tests.
We can't impose a restriction of "no system properties in your
tests" (the thread diverged from Maven's integration tests). Not that
I'm particularly recommending that technique anyway.
- using a system property to enable/disable tests from within
their code
But TestNG looks perfect for this sort of thing. Not sure if you
can dynamically groups so that we could have strategies like
looking in the POM for info and using the standard annotations but
I'm sure it will require some flexibility as it gets more
sophisticated.
I'm all for using test ng for our stuff.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
