I have a unit test that fails sometimes and debugging it is a pain because I don't know why it sometimes fails.
Is there a way inside Eclipse that I can run a JUnit test 5 times or 50 times or something?
Thanks.
- what is that u're trying to test?Venki– Venki2012-01-10 15:03:10 +00:00Commented Jan 10, 2012 at 15:03
- 1IMHO unit tests failing 'sometimes' are useless.home– home2012-01-10 15:12:51 +00:00Commented Jan 10, 2012 at 15:12
- 2Mine too. That's why I want to fix it. I need to run it multiple times so I can diagnose the problem.Thom– Thom2012-01-10 16:14:15 +00:00Commented Jan 10, 2012 at 16:14
- @Thom: Apologies, misunderstood your question.home– home2012-01-10 16:55:58 +00:00Commented Jan 10, 2012 at 16:55
- You can also use the annotation @Repeat(5) to run five timesPrasanna Talakanti– Prasanna Talakanti2012-01-10 21:50:56 +00:00Commented Jan 10, 2012 at 21:50
| Show 5 more comments
4 Answers
I just found the following solution which doesn't require any additional depedency (Spring is required for one of the answers you got).
Run your test with the Parameterized runner:
@RunWith(Parameterized.class) Then add the following method to provide a number of empty parameters equals to the number of times you want to run the test:
@Parameterized.Parameters public static List<Object[]> data() { return Arrays.asList(new Object[10][0]); } This way you don't even have to write a loop. IntelliJ and eclipse also group the results of every iteration together.
Comments
There is a test decorator for this. See Junit API at http://junit.org/apidocs/junit/extensions/RepeatedTest.html
for example
@Test @Repeat(10) public void FailRandomlyNeedToKnowWhy() { .... } 
1 Comment
javanna
The
RepeatedTest decorator comes from JUnit while your code example contains a Spring annotation, isn't it?Inspired on this solution:
Use @Repeat annotation like this:
public class MyTestClass { @Rule public RepeatRule repeatRule = new RepeatRule(); @Test @Repeat(10) public void testMyCode() { //your test code goes here } } You'll only need these two classes:
Repeat.java:
import static java.lang.annotation.ElementType.ANNOTATION_TYPE; import static java.lang.annotation.ElementType.METHOD; import java.lang.annotation.Retention; import java.lang.annotation.RetentionPolicy; import java.lang.annotation.Target; @Retention( RetentionPolicy.RUNTIME ) @Target({ METHOD, ANNOTATION_TYPE }) public @interface Repeat { int value() default 1; } RepeatRule.java:
import org.junit.rules.TestRule; import org.junit.runner.Description; import org.junit.runners.model.Statement; public class RepeatRule implements TestRule { private static class RepeatStatement extends Statement { private final Statement statement; private final int repeat; public RepeatStatement(Statement statement, int repeat) { this.statement = statement; this.repeat = repeat; } @Override public void evaluate() throws Throwable { for (int i = 0; i < repeat; i++) { statement.evaluate(); } } } @Override public Statement apply(Statement statement, Description description) { Statement result = statement; Repeat repeat = description.getAnnotation(Repeat.class); if (repeat != null) { int times = repeat.value(); result = new RepeatStatement(statement, times); } return result; } } 2016-10-25 Edit: In order to use this solution when using @RunWith(PowerMockRunner.class), update to Powermock 1.6.5 (which includes this patch).
1 Comment
JJJ
It took me a bit to verify that it was rerunning, but I noticed that the time increased from 6 seconds to 2 minutes for 1 vs 1000 runs. However, it does not actually create a new run for each, which resulted in me removing a timeout rule I had.