feat(reporter): add ignoreFailedRetries option to avoid duplicate results during retries
#195
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This MR introduces a new reporter option:
ignoreFailedRetries.When enabled, the reporter will skip all failed retry attempts if the test eventually passes. This helps reduce noise and avoids sending multiple results for the same test case.
Why
In Zephyr, each retry attempt can create a separate test result with a different status (e.g. "blocked", "failed") within the same test cycle. This leads to confusion and inflated reporting, even when the test eventually succeeds.
By enabling
ignoreFailedRetries, only the first successful retry is reported — resulting in cleaner and more accurate test cycles.Changes
ignoreFailedRetriesflag to the reporter config (default:false)onTestEndignoreFailedRetriesbehaviorBackward Compatibility