Pathwise

Manuals / Test Automation / Chapter 9

C · Structure · intermediate · Week 5 · Chapter 9 of 12

Reporting, artifacts, and debugging

Green tests are silent. Red tests must scream with context. Learn traces, screenshots, videos, and report formats that make triage fast.

Path progress
69%

Step 1 of 4

Artifact on failure

Screenshot, trace, video, console log — configure your runner to capture on fail only to save disk.

Artifact on failureDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Artifact on failurdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Trigger a failure. Confirm artifact exists and shows the broken state.

Was this step clear?
Chapter learning outcomes
  • Failure artifacts
  • HTML/Allure reports
  • Triage workflow

Clear these before you leave

Side quest

Debug drill

Break a test intentionally. Use trace/screenshot to find root cause in under 10 minutes. Document steps.