Kevin Cooney
Kevin Cooney
@DanielCatz This is a great place to start. The "up-for-grabs" label is used for non-contentious issues that should be moderately easy to resolve. The hardest part of this one would...
@cttillman not sure I understand the question. If you are asking about the tests for JUnit 4.x itself, no we do not use mocking frameworks.
@cttillman Yes, the tests of JUnit 4.x use hand-rolled test doubles (fakes, stubs and mocks).
The Maven Surefire plugin allows to to specify globs (see http://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html). Have you tried that?
@diogoeag I believe it's a problem with the Surefire plugin. You can verify that by writing a class with a main method that uses JUnitCore to run the tests of...
@diogoeag Thanks for the code example. What version of JUnit did you try this on? I think we fixed a related issue in 4.12 but I am not sure.
Thanks. Fixing this would like require changes that are not backwards compatible. Setting milestone to 5.0
@diogoeag but wouldn't we want the parameter name in the description? I think the fixes would best be made on top of the Description builder we are working on for...
@diogoeag we don't yet have a target date for JUnit 5.0, but it would likely be the release after 4.12. We are currently focusing on getting 4.12 out the door
@Fanch- there is no current fix. We thought would fix this on too of the ImmutableDescription work we were working on, but that effort was abandoned.