Is the only reason to upgrade to junit 4, to get the parallelization possibility (which isn't sounding very compelling!)?
Ie, making our unit tests lean is fully independent of junit 4? Mike On Wed, Nov 25, 2009 at 4:17 PM, Uwe Schindler <u...@thetaphi.de> wrote: >> junit 4 parallelization is still in its infancy. I think the docs for it >> are just in the changes file that it was first released with. That >> version had severe bugs that made it almost unusable - I think thats >> mostly fixed in a newer release. There is also a much better impl of one >> of the key classes (I think they call it computer) written by someone >> else that will eventually go into the code base I think (written by the >> guy(s) that I think found/fixed the initial buggy-ness) - essentially, I >> think its still unbaked. > > There is another problem. Parallelization would only work with tests, that > do not change gloabl defaults. E.g. LocalizedTestCase changes the default > locale. If another test would run in Paralale, it would break. > > Son only isolated tests can run in parallel. This LocalizedTestCase cannot > solved in another way. The same would have been in 2.9 with the > TokenStream.useOnlyNewAPI switch, but this is now longer the case for 3.1. > > Uwe > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
