Thanks for your help Konstantin!!! the "simple" problem is that the bigger part of tests inherit from OgnlTestCase that are ctors-based parametrized test cases (they launch the Suite), so when porting it to JUnit4 using the @RunWith(Parameterized.class), half tests are broken :/ Simo
http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Mon, May 16, 2011 at 1:21 AM, Konstantin Kolinko <knst.koli...@gmail.com> wrote: > 2011/5/15 Simone Tripodi <simonetrip...@apache.org>: >> Hi all guys, >> please help me, there's the need of a volunteer with fresh mind that >> could review patch attached to OGNL-9. I put too much effort on >> refactoring that I can't see where the error is. >> I hope Gary can help us since IIUC he's our JUnit guru!!! >> Now off to bed, it's 1:00am :P >> Have a nice WE, >> Simo >> > > Maybe it is possible to go incrementally, changing small number of > tests in a step? > > I thought JUnit4 runners should autodetect JUnit3 tests. At least I > think it is possible to force it with @RunWith(JUnit38ClassRunner), > but JUnit38ClassRunner is in the "internal" package and thus is not > supposed to be used explicitly. > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
