Due to the order of JUnit execution of rules and life-cycle methods (@After), Geb does not report failures because failureTracker flag is set AFTER writeGebReport() is called so it will never be true.
This issue is similar to the #445. Possible solution is explained in junit-team/junit4#906 , but it is not simple since the browser instance is null when the TestWatcher is called.
Due to the order of JUnit execution of rules and life-cycle methods (
@After), Geb does not report failures becausefailureTrackerflag is set AFTERwriteGebReport()is called so it will never be true.This issue is similar to the #445. Possible solution is explained in junit-team/junit4#906 , but it is not simple since the
browserinstance is null when the TestWatcher is called.