Repository navigation
feat(failure-intel): retry- and history-aware test status (#141) - #152
Merged
Merged
Conversation
Each test gets a status from this run's retries and the earlier runs in target/metrics-history/: passed on retry, newly failing, consistently failing, intermittent. A pure classify() function, wired into the metrics export (testStatus), shown in a card next to the Flakiness Radar and as a badge in the failure detail. Newly failing tests are listed first in the Failures tab. Radar thresholds and failOnHighFlakiness are unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…get (#141) Builds that clean target/ or discard the CI workspace between runs had no metrics history, so the Flakiness Radar and the newly/consistently-failing and intermittent statuses were always empty. History can now live anywhere: -Dseleniumboot.history.dir, then flakiness.historyDir, then the existing <reports dir>/metrics-history default. Documented with a CI cache recipe. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
Author
|
Added 🤖 Generated with Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 & why
Flakiness was a pass/fail ratio only and ignored retries. Each test now gets a status from this run's retries and the earlier runs in
target/metrics-history/:A test that passed first time, or has no history, gets no status (except passed on retry).
TestStatusAnalyzer.classify(...)is a pure function;forRun(...)reads the history.exportToJson()before this run's history copy is written, and files written by this JVM are excluded, so a run is never compared with itself (TestNG firesonFinishper suite).testStatus.failOnHighFlakiness.Part of #138. Closes #141.
Verification
mvn test: 659 run, 0 failures (638 on master + 21 new): empty history, single run, skipped runs, unreadable history file, double export in one JVM, report ordering.Notes
🤖 Generated with Claude Code