You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(test): add failure triage for batch root-cause grouping
Add testsprite test failure triage --project <id> to group failed tests into root-cause clusters using existing M2.1 analysis fields. Returns a representative test per cluster, confidence score, and fix priority without downloading failure bundles.
Includes grouping library, command wiring, unit/integration tests, docs, CHANGELOG entry, agent skill update, and help snapshot.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,10 @@ All notable changes to `@testsprite/testsprite-cli` are documented here. The for
4
4
5
5
## [Unreleased]
6
6
7
+
### Added
8
+
9
+
-**`test failure triage --project <id>`** — groups all failed tests in a project into root-cause clusters using existing M2.1 analysis fields (`failureKind`, `recommendedFixTarget.reference`, `rootCauseHypothesis`). Returns a representative test per cluster, affected test ids, confidence score, and fix priority — without downloading failure bundles. Supports `--type`, `--filter`, and `--max-concurrency`. Client-side Phase-0 triage until native backend clustering ships.
testsprite test failure summary test_xxxxxxxx --dry-run --output json
249
249
```
250
250
251
+
#### `testsprite test failure triage --project <id>`
252
+
253
+
When many tests fail in the same project, triage them into a few root-cause clusters before downloading bundles. The CLI lists all failed tests, fetches a lightweight `failure/summary` per test (no screenshots or video), and groups them client-side by:
4. singleton (one test per cluster when no shared signal exists)
259
+
260
+
Each cluster includes a `representativeTestId`, `memberTestIds`, `confidence`, and `fixPriority` (lower = fix first). After triage, pull one bundle from the representative test:
261
+
262
+
```bash
263
+
# Triage all failed tests in a project
264
+
testsprite test failure triage --project proj_xxxxxxxx --output json
265
+
266
+
# Limit to backend tests whose name contains "checkout"
||`test failure get`| The agent entry point: one self-contained latest-failure bundle |
103
103
||`test failure summary`| One-screen triage card (no media download) |
104
+
||`test failure triage`| Group all failed tests in a project into root-cause clusters (no bundle download) |
104
105
|**Write**|`test create` / `test create-batch`| Create a test (or bulk-create from a plan file); `--produces` / `--needs` / `--category` wire BE dependency metadata |
0 commit comments