Triage & diagnostics

When a test run finishes with multiple failures, you don't want to investigate each one cold. Cofactor's triage groups related failures by likely root cause and attaches per-failure diagnostics, so you start from causes instead of symptoms.

01How triage works

After a test run completes, Cofactor runs triage over its failures:

1. It collects a diagnostic for each failed workflow run — an analysis of why that run failed.
2. It clusters failures that likely share a root cause.
3. It ranks the clusters by severity and surfaces the most pressing one first.

You'll find this in the Triage tab on a completed test run.

02Reading the clusters

Each cluster represents one likely root cause and carries a title, a severity, the number of failures it covers, a summary, and a suggested next action. Start with the highest-ranked cluster, read its summary, then open the workflow runs grouped under it to confirm the cause before moving on.

Clusters also mark failures that are new — failing for the first time — so you can separate fresh regressions from ongoing breakage.

03Triage states

While triage is preparing, the tab shows its progress:

If triage is Skipped or Failed, fall back to the workflow list and the per-run failure investigation flow.

04Per-failure diagnostics

A failure diagnostic is the analysis behind a single failed workflow run — produced asynchronously, then attached to the run and to any issue occurrence it generated. Open a failed workflow run to read its diagnostic alongside the steps, assertions, and recording. Triage clusters are built from these diagnostics, so the cluster tells you the shared cause while each diagnostic explains an individual failure.

05Related

• Test runs — where triage appears
• Workflow runs — per-run failure investigation
• Issues — defects filed from failures
• Runs & results