Skip to main content

Failure classification

Failure classification keeps a test suite useful. Qodex does not treat every red run as a product bug. It first decides whether the failure is a real bug, a stale test, or an environment issue.

The three classes

Why this matters

Without classification, a renamed button, a staging outage, and a real authentication regression all look the same. That creates noisy reports and missed bugs. With classification:
  • Selector drift becomes a stale-test task.
  • Staging downtime becomes an environment note.
  • Product regressions become findings.

Examples

Security note

For security scenarios, the classifier still runs first. If the failure is a real bug, security rules then interpret it with inverted semantics: fail means the app allowed the attack.

Severity model

See how real bugs get impact-ranked.

Triage workflow

Review what happens after a finding opens.

Re-run failed tests

Confirm fixes and flaky failures.

Scenarios

Understand the test unit that can go stale.