Artifacts
Reference
Most of the product’s value shows up in the artifacts it writes. Treat these files as part of the operating model, not temporary scratch output.
Output root
Most useful artifacts live under one working directory
That makes it easier to archive them in CI, inspect them locally, and feed them into release reviews or downstream tooling.
Artifact root
Default working directory
<testsRoot>/.e2e-ai-agents/
Core Planning Artifacts
| File | Produced By | What It Is For |
|---|---|---|
plan.json | plan | Structured coverage plan with impacted families, run sets, confidence, and decisions |
ci-summary.md | plan | Markdown summary for PR comments or release reports |
metrics.jsonl | plan | Append-only event log for metrics and later cost reporting |
metrics-summary.json | plan | Aggregated metrics for dashboards or CI summaries |
Knowledge And Training Artifacts
| File | Produced By | What It Is For |
|---|---|---|
route-families.json | train or bootstrap | The core manifest mapping code paths to product areas and flows |
train-report.json | train | Training stats, coverage numbers, and enrichment timing |
traceability.json | traceability-ingest | Rolling file-to-test mapping manifest |
traceability-state.json | traceability-ingest | Hit counts and rolling ingest state |
failure-history.json | failure correlation | Historical file-to-failure relationships used for confidence boosts |
AI And QA Artifacts
| File or Directory | Produced By | What It Is For |
|---|---|---|
generated-needs-review/ | generation stage | Quarantine area for specs blocked by hallucination guardrails or verification failures |
qa-screenshots/ | impact-gate-qa | Browser screenshots captured during exploratory testing or fix verification |
reports/ | reporting flows | Structured outputs consumed by downstream tooling or humans |
How Teams Usually Use Them
Operating model
How teams usually work with the artifacts
plan.jsonfeeds automation and deeper toolingci-summary.mdis posted into PRs or release discussionsroute-families.jsonis maintained as product knowledgetraceability.jsonimproves precision over timegenerated-needs-review/becomes a manual review queue
Practical habit
Inspect the written artifacts, not just stdout
The artifacts are the easiest way to understand what the tool decided, why it made that decision, and what a release owner or QA lead should do next.