9. Reporting, artifacts, and debugging
Test Automation · 48 pages source format
Green tests are silent. Red tests must scream with context. Learn traces, screenshots, videos, and report formats that make triage fast.
What you'll learn
- Failure artifacts
- HTML/Allure reports
- Triage workflow
Artifact on failure
Screenshot, trace, video, console log — configure your runner to capture on fail only to save disk.
Do this now
Trigger a failure. Confirm artifact exists and shows the broken state.
Readable test names
test_login_with_locked_user_shows_error_message beats test_3. Names are documentation.
Do this now
Rename all tests to describe behavior. No test1, test2.
Report for humans
HTML report or Allure gives PMs and devs a dashboard. JSON logs alone do not scale teams.
Do this now
Generate an HTML report locally. Open it and find a failed test in under 30 seconds.
Triage ritual
Define: who owns red builds, SLA for fix, flake vs bug classification.
Do this now
Write TRIAGE.md — 5 lines: owner, SLA, artifact location, flake definition, escalation.