Repository navigation
feat(failure-intel): rule-based failure classification - #148
Merged
Merged
Conversation
Tags each failed test with a category and the evidence for it from the exception class chain and message. Shown in the HTML report failure panel, the metrics JSON and the JUnit XML. No AI, no network; UNKNOWN is valid. Closes #139 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
1 participant
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
Part of Failure Intelligence (#138). Each failed test now gets a category and the evidence for it, using only the error message and stack trace the framework already records. No AI, no network.
FailureClassifier.classify(TestTiming)is a pure function returning category + short evidence.LOCATOR_NOT_FOUND,ELEMENT_NOT_INTERACTABLE,STALE_ELEMENT,TIMEOUT,ASSERTION_MISMATCH,NAVIGATION_ERROR,BROWSER_CRASH,UNKNOWN.LocatorExceptioncaused byTimeoutExceptionisLOCATOR_NOT_FOUND, while a bareTimeoutExceptionisTIMEOUTand a renderer/page-load timeout isNAVIGATION_ERROR.failureCategory/failureEvidencein the metrics JSON;typeon<failure>in the JUnit XML.Closes #139
Notes
TestTimingdoes not carry them. Left for feat(failure-intel): detail record per failure, reused by AI analysis #142 (richer AI context) where they are collected anyway.<failure type>was previously absent; it is now the category, and the body gains one[CATEGORY] evidenceline before the stack trace.Verification
mvn test: 605 run, 0 failures (18 newFailureClassifierTestcases).🤖 Generated with Claude Code