Atlas › 01 Agent Skills for Browser Automation › CI/CD Integration for AI-Driven Browser Tests☰ Read as one page
CI/CD Integration for AI-Driven Browser Tests
12.1Principles1. Headless in CI — no display available; --headed is a local-development flag 2. Fresh session per test — one named session (-s=name) per…12.2GitHub Actions ConfigurationTwo things changed from the 2025-era setups worth noticing: browser and system dependencies come from Playwright's own installer (npx…12.3Test Runner ScriptA candid note on this script: hard-coding refs (e3, e4) in a shell script works only for pages whose snapshot layout is stable. That's fine…12.4Docker Configuration(You can also start from Microsoft's official Playwright image — mcr.microsoft.com/playwright:v1.61.0-noble — which ships browsers and…12.5Parallel Execution in CIEach test group runs as a separate job with its own browser instance. fail-fast: false ensures all groups run even if one fails.12.6Artifact ManagementThe trace row is the important 2026 addition. If an AI agent drove a browser in your pipeline and you cannot answer "show me exactly what…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…