junit4 icon indicating copy to clipboard operation
junit4 copied to clipboard

A programmer-oriented testing framework for Java.

Results 111 junit4 issues
Sort by recently updated
recently updated
newest added

Rules is a nice mechanism for composing rather than inheriting functionality. This concept could be extended to suites as well, like the @BeforeClass/@AfterClass annotation on a suite. Also, by being...

feature
rules

A lot of APIs in Android deal with `CharSequence`. And using `assertEquals()` with `CharSequence` arguments is cumbersome and unstable. One has to reproduce the exact same type which might change...

feature
up-for-grabs

When using the Parameterized runner there is no possibility to run only a test method of a test class. For example when running in maven: mvn test -Dtest=TesClass#testName No tests...

feature
parameterized

MethodRule only gets invoked for the test method, however for a change where you would otherwise extend BlockJUnit4ClassRunner and override withBefores, you can't achieve the same with a Rule. MethodRule...

feature
rules

in this example: @RunWith(Enclosed.class) public class OuterClassTest { @Before public void startStore() throws Exception { ... } @Test public void outerTest1() { ... } public static class PoolTest extends JedisPoolTestBase...

feature

Since the new TestRule interface some behaviours have change in the execution order of the @Rules. We have one rule which records Test Results. That Rule implements MethodsRule. Now in...

rules

There's no documentation on how to create a custom RunnerBuilder.

It would be useful to be able to add package level annotations to package-info.java. For example adding @org.junit.Ignore to the package should ignore all tests in that package.

Currently doing this ``` java @Datapoints function Browser[] getBrowserAndStuff() @Theory function void theoryBrowse( Browser browser ) { setStuff( browser.getStuff() ); stuff.do(); } @Theory function void theoryBrowseMore( Browser browser ) {...

feature
theories

When debugging or profiling highly threaded tests, leaving the JUnit timeout threads as "Thread-#" is not very useful. The obvious name for threads would probably be the full name for...

up-for-grabs