From looking at TestNG, it is pretty cool, but we've already figured
workarounds for most of the JUnit shortcomings. This is similar to
Ant/Maven switch in that it probably makes things better on the long
run, but buys us close to nothing on the short run and will be
disruptive to what we are doing at the moment.
So I suggest to do one thing at a time. I think Maven switch will be
traumatic enough :-)
Andrus
On Feb 27, 2006, at 6:31 PM, Kevin Menard wrote:
> This week is going to generally be hell for me, but next week opens
> up a
> bit, so I intend on reading through the spec and looking at the JPA
> stuff
> more closely. It doesn't look like a terrible amount has been
> accomplished
> in this space thus far though, so it's probably not a big deal. I
> just
> wanted to let you guys know.
>
> Additionally, since the JPA work is going to be the guinea pig for
> maven 2,
> did we want to give TestNG a try as well? I know that idea has
> been batted
> around briefly before. If we're happy with JUnit, then I'm fine with
> sticking with it, but TestNG does have some nice features.
>
> --
> Kevin
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Feb 28 2006 - 05:16:31 EST