How can Spock be made to retry failed Geb tests?

Question

I have functional tests for a Grails app which use Geb and Spock. Occasionally, a functional test will fail for timeouts or other sporadic behavior. In previous projects using TestNG, I'd have a retryAnalyzer just trigger a retry during test execution to see if it fails both times (and then fail for real).

How do I get Spock to retry a failed test?

score 9 · Answer 1 · answered Oct 12 '13 at 17:54

I know this question is a year old, but we've been having the same problem. Following Peter's suggestion, I created a Spock extension (https://github.com/anotherchrisberry/spock-retry).

If you have a base specification (which was our case), you can just add a @RetryOnFailure annotation to it:

@RetryOnFailure
class BaseFunctionalSpec extends Specification {
    //    all tests will execute up to two times before failing
}

Or, you can add it to a specific feature:

class SomeSpec extends Specification {

    @RetryOnFailure(times=3)
    void 'test something that fails sporadically'() {
        // will execute test up to three times before failing
    }
}

I look forward to giving this a try. – John Flinchbaugh Oct 29 '13 at 21:42 — John Flinchbaugh, Oct 29 '13 at 21:42
this is the best extension – Tomas Lin Jun 25 '15 at 18:14 — Tomas Lin, Jun 25 '15 at 18:14

score 2 · Answer 2 · answered Jul 13 '12 at 18:37

2

You'd have to write a little JUnit rule (for example something like https://gist.github.com/897229) or Spock extension. You'd probably have to live with some limitations like the same spec instance being reused and JUnit just reporting a single test, but hopefully nothing that rules out the approach altogether. (One thing that comes to mind is that mocking might not work.) In a future version of Spock, repeating a test (or its building blocks) will likely become a first-class concept, doing away with these limitations.

answered Jul 13 '12 at 18:37

Peter Niederwieser

121,412
21
324
259

I've finally gone down the junit rule route, and added a class similar to the one here: http://stackoverflow.com/questions/8295100/how-to-re-run-failed-junit-tests-immediately . I put println statements around the base.evaluate() call, and I can tell my rule is being run, but I'm finding that it always *returns*, and I never see a Throwable thrown, even on failure. Is there another way to tell the test failed? – John Flinchbaugh Oct 19 '12 at 17:31

How can Spock be made to retry failed Geb tests?

2 Answers2