E2E Testing Workflow

Overview

Specialized workflow for end-to-end testing using Playwright including browser automation, visual regression testing, cross-browser testing, and CI/CD integration.

When to Use This Workflow

Use this workflow when:

• Setting up E2E testing
• Automating browser tests
• Implementing visual regression
• Testing across browsers
• Integrating tests with CI/CD

Scope and proof

Choose phases needed for the current task, not every listed skill. Use dedicated test accounts, isolated fixtures and approved sandbox endpoints; clicks can send messages, make purchases or delete data. Review browser installation/downloads and CI permissions first. Traces, screenshots, videos and storage-state files can contain credentials or private data; keep them private and redact artifacts before sharing. A Playwright WebKit run is not proof on actual Safari/iOS, and mobile emulation is not a real-device test. Keep visual baselines fixed until differences are reviewed; do not overwrite them merely to get a pass.