I have similar experience. I upgraded a couple of projects to JUnit 4.8.1 (from 3.x) in the past few months. Leaving the old tests as-is has worked fine, while allowing me to write new tests in the new style, just as you propose.
Seems like the best approach to me. ~Daniel Siegmann -----Original Message----- From: Julien HENRY [mailto:henr...@yahoo.fr] Sent: Wednesday, June 09, 2010 8:29 AM To: Maven Developers List Subject: Re : Moving to TestNG JUnit4? > JUnit 4 apparently runs JUnit 3 tests out of the box I can confirm that (starting from JUnit 4.7 if I remember correctly). I usually upgrade all my projects to JUnit 4. This way I can write new tests using JUnit 4 style and keep old tests with JUnit 3 style. My 2 cts ++ Julien ----- Message d'origine ---- > De : Mark Derricutt <m...@talios.com> > À : Maven Developers List <dev@maven.apache.org> > Envoyé le : Mer 9 juin 2010, 14h 24min 56s > Objet : Re: Moving to TestNG JUnit4? > > JUnit 4 apparently runs JUnit 3 tests out of the box, so one could > feasibly change the dependencies to JUnit 4 at least. I understand the > reasons for not physically changing old tests for the sake of change > tho. Mark -- Pull me down under... On Tue, Jun 8, 2010 > at 6:29 AM, Jason Chaffee < > href="mailto:jchaf...@ebates.com";>jchaf...@ebates.com> wrote: > > FYI, JUnit now supports concurrent running of tests. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
