73 / 168 · 01 Agent Skills for Browser Automation · Architecture Decision Records for an AI Test Automation Framework← prev⊞ allnext →☰ Read as one page
10.7ADR-007: Test Result Reporting
Context
Test results need to be consumable by:
- The AI agent (for reasoning about pass/fail)
- Developers (for debugging)
- CI systems (for pass/fail gates)
Decision
Three output formats:
Console output (for CI):
PASS login_valid_credentials (2.3s)
PASS login_invalid_password (1.8s)
FAIL login_expired_account (5.1s) — Expected "Account expired", got "Welcome"
PASS signup_new_user (3.2s)
4 tests: 3 passed, 1 failed
JSON report (for programmatic consumption):
{
"suite": "authentication",
"tests": [
{
"name": "login_valid_credentials",
"status": "pass",
"duration_ms": 2300,
"commands": ["open", "snapshot", "fill", "fill", "click", "snapshot"],
"artifacts": ["login_step1.png", "login_result.yaml"]
}
]
}
Failure artifacts (for debugging):
failures/
├── login_expired_account/
│ ├── screenshot.png
│ ├── snapshot.yaml
│ ├── page_url.txt
│ ├── trace.zip # when produced by a runner/healer session
│ └── agent_reasoning.md