Test Results

Read when:

• adding result formats;
• changing how failed tests are summarized;
• debugging why crabbox results has no data.

Crabbox can attach JUnit XML summaries to coordinator run history. The agent uses this so a failed run can answer "which tests failed?" without scraping a large log tail.

Configure per run:

crabbox run --id cbx_... --junit junit.xml -- go test ./...

Or per repo:

results:
  junit:
    - junit.xml
    - reports/junit.xml

After the command exits, the CLI reads those remote files from the workdir, parses JUnit, and sends only the summary to the coordinator. Raw XML is not stored. The coordinator caps stored file lists, failed-case entries, and long strings so a huge report cannot exceed Durable Object storage or response limits.

Use:

crabbox history --lease cbx_...
crabbox results run_...

Current format support:

• JUnit XML.

Future useful additions:

• Vitest JSON;
• Go test2json;
• flaky history across runs;
• changed-file correlation.