12.7Interview Talking Point

"Our CI pipeline runs browser tests through the Playwright CLI — headless, one named session per test for isolation, torn down after each run. Browsers and system deps come from npx playwright install --with-deps, so there's no hand-maintained library list. We parallelize with a GitHub Actions matrix across test groups, and within a job by giving each worker its own session name. On failure we capture a screenshot, the YAML accessibility snapshot, and the current URL; for agent-driven and healer runs we also archive Playwright traces, which since 1.60 include HAR network capture — that's our audit trail for what the AI actually did in the browser. The scripted smoke layer is deliberately thin: anything that needs resilience is either agent-executed or promoted to generated Playwright specs."