Very constrained environment. No 1.5 and preferences for fewer
imports. Probably not a big deal, but I was doing a fairly narrow
thing for a client, and JUnit and TestNG both added complexity to what
I was doing. Probably won't ever use them again, but I mostly can't
see the advantage of JUnit over POJO in maven, except for UI
convenience. TestNG, on the other hand, can do thread-pooled tests,
so I will often use that.
Christian.
On 13-May-08, at 21:18 , Dan Fabulich wrote:
Christian Edward Gruber wrote:
Moving on to future efforts, I added the final step in support for
setup/teardown of fixture in the PojoTestSet.
Patch appreciated; it will be considered for the next Surefire
version.
I didn't know people really used the Pojo tests, partly because I've
never understood what they're good for. Why not just use JUnit?
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]