Test failure root cause classification and triage

Description:

When viewing a specific test failure, there’s no way to classify the root cause from a development/triage perspective. This makes it hard to:

• Quickly identify which failures need immediate attention vs. known issues

• Measure test suite health accurately

• Prioritize engineering effort appropriately

Proposed Solution:

A manual classification/tagging system for test failures that allows users to categorize the root cause when viewing individual test failures. Suggested categories:

• Product Bug — Actual defect in the application

• Flaky Test — Intermittent failure due to test instability

• Environment Issue — Infrastructure, network, or test environment problems

• Test Bug — Issue with the test code itself

• Known Issue — Linked to an existing tracked bug (e.g., JIRA)

• Under Investigation — Not yet triaged

Note: This is different from Currents’ existing automatic error classification (Category, Action, Target), which identifies what technically caused the error from the test’s perspective. This feature would add manual triage classification to indicate which part of the development cycle is responsible for the failure.

Benefits:

• Enable error identification and triage directly from the test failure view

• Quickly determine what action to take on each test error

• Better visibility into failure root causes

• More accurate test suite health metrics

• Improved prioritization of engineering work

Use Case:

When viewing a specific test failure, users should be able to classify it to indicate whether it’s a product bug requiring immediate attention, a known flaky test, an environment issue, or something under investigation.