On 04/15/2010 11:21 PM, Justin Lee wrote:
> OK. So i have some questions for everyone. We dont have to answer
> them now, but perhaps at next week's tech meeting if us Oracle types
> are not tied up in planning meetings next week.
>
> 1. Given that the tests don't run successfully on 1.5 for some
> strange reason, do we want to maintain 1.5 compatibility for the
> 1.9 branch? I'm currently running a release on a 1.6 VM and
> targetting the 1.5 byte code. While this generates (hopefully)
> 1.5 compliant byte code, it doesn't really catch when we use 1.6
> only classes like I did in websockets. If everyone still needs
> 1.5 compatbility I guess we can hobble along like this. I know
> we talked about that a while back but it's still a burr in my
> saddle so to speak that we have to jump through hoops like
> this. If we stay with 1.5, we need to figure out why the tests
> crash on a 1.5 VM.
>
I can't really comment on this since we are using Grizzly 2 in OpenDS
(which already depends on JDK6).
> 1. Does anyone have any objections to me migrating our tests from
> junit to testng? I much prefer testng and we get quite a bit
> more control and features for very little effort. This is
> probably the least contentious of the two but I wanted to throw
> that out there.
>
>
We've been using TestNG for years with OpenDS and found it to be very
good and stable. I seem to remember that we used an automated mechanism
for migrating our JUnit tests to TestNG, perhaps this:
http://testng.org/migrating.html?
We've not fully taken advantage of the parallel support in TestNG
basically because we have too many mutable singletons within the server
(this prevents us from isolating tests from one another).
Matt