momentic-result-classification

What it does

• What is the test's intended behavior?
• What is the earliest divergent step/container?
• What did that step intend to do?
• Which element/state did it actually interact with or observe?
• What changed in the screenshot, URL, DOM, trace, or recovery log after the step?
• Why is the later failure a consequence of that earlier divergence?
• Screenshots are the default truth source for page state. Use trace fields and DOM/HTML to explain why the screenshot changed or did not change.

Requirements & configuration

• 1. Call the momenticlistruns tool to identify the runs you want more detail on. Always pass gitBranchName when it exists on the run in question. Omit it when you need runs from other branches.
• You need to determine whether there was an application or test change between runs by analyzing the screenshots and other run data.
• Examples: an application change that requires a test update; vague locators or assertions that can be rewritten to pass stably.
• NONRECOVERABLE — The failure cannot be automatically addressed and requires manual intervention.
• TESTSETUP — Missing test data or files necessary to run the test, where the fix requires user action outside of the test itself.

Configuration: INFRARECOVERABLEONE_TIME_RECOVERABLENON_RECOVERABLENO_FAILUREAPPLICATION_CHANGETEST_AUTHORSHIPTEST_SETUP