Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Implemented
-
None
Description
If flaky-test-check is triggered with specific method, it checks if the method exists in the test class. This does not work for test methods inherited from parent class (of which there will be more and more). I propose removing this safety check. If the specified method cannot be run, build output will show Tests run: 0.
Attachments
Issue Links
- is related to
-
HDDS-10080 Let junit.sh fail if no tests were matched in repeated run
- Resolved
- links to