Details
-
Test
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Currently, our repeat test tasks merge the output from all executions of a given test class, making it very difficult to diagnose failures in repeat tests.
CAUSE:
In order to run tests repeatedly, our repeat test tasks override Gradle code to allow a test class to execute more than once.
Gradle directs the output from each test to a log associated with the test class name.
SOLUTION:
Change Gradle to distinguish separate executions of a test class, and to log the output from each execution separately. This can be done by using a custom "test result processor" that appends an iteration counter to the end of the test class name before processing the result.