If we switch to a snapshot release, that means the version of junit will be a moving target, right? So if someone checks a breaking change into junit all of our builds will fail. Or worse, not fail. I'm not sure if that's state we want to be in.
-Dan On Tue, May 10, 2016 at 2:54 PM, Jens Deppe <[email protected]> wrote: > Kirk recently found that test classes annotated with both @Category and > @Parameterized (both standard JUnit annotations) result in tests being > skipped [1] > > It appears that JUnit 4.13-SNAPSHOT fixes the issue. > > Does anyone have any aversion to using a 'SNAPSHOT' release for junit? > > An alternative is to use JunitParamsRunner [2]. However I've already run > into a problem with it in that params are not exposed to @Before methods > which means that any @Before code, using parameters, would need to be > explicitly called from every test method. > > Thoughts? Comments? > > --Jens > > > [1] https://issues.apache.org/jira/browse/GEODE-1350 > [2] http://pragmatists.github.io/JUnitParams/ >
