e2e-testing – Coding skill for AI agents

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.

Workflow Phases

Phase 1: Test Setup

Skills to Invoke

• playwright-skill - Playwright setup
• e2e-testing-patterns - E2E patterns

Actions

1. Install Playwright

2. Configure test framework

3. Set up test directory

4. Configure browsers

5. Create base test setup

Copy-Paste Prompts

Use @playwright-skill to set up Playwright testing

Phase 2: Test Design

Skills to Invoke

• e2e-testing-patterns - Test patterns
• test-automator - Test automation

Actions

1. Identify critical flows

2. Design test scenarios

3. Plan test data

4. Create page objects

5. Set up fixtures

Copy-Paste Prompts

Use @e2e-testing-patterns to design E2E test strategy

Phase 3: Test Implementation

Skills to Invoke

• playwright-skill - Playwright tests
• webapp-testing - Web app testing

Actions

1. Write test scripts

2. Add assertions

3. Implement waits

4. Handle dynamic content

5. Add error handling

Copy-Paste Prompts

Use @playwright-skill to write E2E test scripts

Phase 4: Browser Automation

Skills to Invoke

• browser-automation - Browser automation
• playwright-skill - Playwright features

Actions

1. Configure headless mode

2. Set up screenshots

3. Implement video recording

4. Add trace collection

5. Configure mobile emulation

Copy-Paste Prompts

Use @browser-automation to automate browser interactions

Phase 5: Visual Regression

Skills to Invoke

• playwright-skill - Visual testing
• ui-visual-validator - Visual validation

Actions

1. Set up visual testing

2. Create baseline images

3. Add visual assertions

4. Configure thresholds

5. Review differences

Copy-Paste Prompts

Use @playwright-skill to implement visual regression testing

Phase 6: Cross-Browser Testing

Skills to Invoke

• playwright-skill - Multi-browser
• webapp-testing - Browser testing

Actions

1. Configure Chromium

2. Add Firefox tests

3. Add WebKit tests

4. Test mobile browsers

5. Compare results

Copy-Paste Prompts

Use @playwright-skill to run cross-browser tests

Phase 7: CI/CD Integration

Skills to Invoke

• github-actions-templates - GitHub Actions
• cicd-automation-workflow-automate - CI/CD

Actions

1. Create CI workflow

2. Configure parallel execution

3. Set up artifacts

4. Add reporting

5. Configure notifications

Copy-Paste Prompts

Use @github-actions-templates to integrate E2E tests with CI

Quality Gates

• [ ] Tests passing
• [ ] Coverage adequate
• [ ] Visual tests stable
• [ ] Cross-browser verified
• [ ] CI integration working

Related Workflow Bundles

• testing-qa - Testing workflow
• development - Development
• web-performance-optimization - Performance

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.