Retry Mechanism For Failed Tests For 'N' times

[anas-baadshah]

Do we have a mechanism to rerun the failed tests 'n' times. As I can see the re-run by file mechanism cannot be implemented since I can see a comment from the cuckulater example

/**
 * The CucumberOptions annotation is mandatory for exactly one of the classes in the test project.
 * Only the first annotated class that is found will be used, others are ignored. If no class is
 * annotated, an exception is thrown. This annotation does not have to placed in runner class
 */

How can we implement a retry mechanism? Any advice/ docs?
Thanks

[lsuski]

Maybe this would require small change in CucumberAndroidJUnitRunner to be able to find another class with rerun file specified, e.g. with some specific annotation. Rerun file itself must be located on the device. Searching this class instead of default one would determined by instrumentation runner argument. This would require PR

[lsuski]

No work on my side. In general I don't find it good approach and I invest my time to make tests reliable amd to find cause of failures