Skill

role-aqa:e2e-testing

End-to-end test automation with Playwright (codegen, trace viewer, MCP, sharding, visual comparisons, fixtures, component testing), Cypress v13, Selenium 4 (BiDi), WebdriverIO, TestCafe, Robot Framework. Visual regression: Percy, Chromatic, Applitools, BackstopJS, Lost Pixel. Cross-browser: BrowserStack, Sauce Labs. Accessibility in E2E.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-aqa

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

- Setting up or extending an E2E test suite (Playwright, Cypress, Selenium, WebdriverIO)

Supporting Assets

references/cypress-selenium-alternatives.mdreferences/playwright-core.mdreferences/pom-accessibility-flaky-tests.mdreferences/visual-regression-cloud-testing.md

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

ai-first-engineering

Provides process, architecture, review, hiring, and testing guidelines for engineering teams relying on AI code generation.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-aqa:e2e-testing

When to use

Setting up or extending an E2E test suite (Playwright, Cypress, Selenium, WebdriverIO)

Writing reliable locators, fixtures, or multi-browser project configs in Playwright

Adding visual regression testing (Percy, Chromatic, Applitools, BackstopJS)

Running cross-browser tests on BrowserStack, Sauce Labs, or LambdaTest

Adding accessibility checks (axe) to existing E2E flows

Debugging or quarantining flaky tests

Choosing a framework for a team that includes non-developer testers

Core principles

Auto-wait over sleep — Playwright's auto-wait eliminates race conditions; any sleep() in tests is a bug waiting to happen

Locator hierarchy matters — role > label > placeholder > text > testId > CSS; resilience decreases from left to right

Fixtures own setup and teardown — create data via API before tests, clean up after; never rely on pre-existing state

Flaky = broken — a test with >2% unreliable failure rate is a broken test; quarantine and fix, never retry into silence

Visual tests need masking — dynamic content (prices, timestamps, avatars) must be masked before snapshotting or diffs are noise

Reference Files

references/playwright-core.md — auto-wait, locator hierarchy, fixtures, test.step, multi-browser projects, sharding, API testing, component testing, visual comparisons, MCP integration

references/cypress-selenium-alternatives.md — Cypress v13 (session, intercept, component testing, multi-origin), Selenium 4 (BiDi, relative locators, CDP, Grid), WebdriverIO, TestCafe, Robot Framework, CodeceptJS

references/visual-regression-cloud-testing.md — Percy, Chromatic, Applitools, BackstopJS, Lost Pixel, reg-suit; visual testing best practices; BrowserStack, Sauce Labs, LambdaTest setup

references/pom-accessibility-flaky-tests.md — Page Object Model with TypeScript, playwright-axe and cypress-axe integration, WCAG assertions, flaky test detection and quarantine workflow, test data patterns

E2E Testing

When to use

Setting up or extending an E2E test suite (Playwright, Cypress, Selenium, WebdriverIO)
Writing reliable locators, fixtures, or multi-browser project configs in Playwright
Adding visual regression testing (Percy, Chromatic, Applitools, BackstopJS)
Running cross-browser tests on BrowserStack, Sauce Labs, or LambdaTest
Adding accessibility checks (axe) to existing E2E flows
Debugging or quarantining flaky tests
Choosing a framework for a team that includes non-developer testers

Core principles

Auto-wait over sleep — Playwright's auto-wait eliminates race conditions; any sleep() in tests is a bug waiting to happen
Locator hierarchy matters — role > label > placeholder > text > testId > CSS; resilience decreases from left to right
Fixtures own setup and teardown — create data via API before tests, clean up after; never rely on pre-existing state
Flaky = broken — a test with >2% unreliable failure rate is a broken test; quarantine and fix, never retry into silence
Visual tests need masking — dynamic content (prices, timestamps, avatars) must be masked before snapshotting or diffs are noise

Reference Files

references/playwright-core.md — auto-wait, locator hierarchy, fixtures, test.step, multi-browser projects, sharding, API testing, component testing, visual comparisons, MCP integration
references/cypress-selenium-alternatives.md — Cypress v13 (session, intercept, component testing, multi-origin), Selenium 4 (BiDi, relative locators, CDP, Grid), WebdriverIO, TestCafe, Robot Framework, CodeceptJS
references/visual-regression-cloud-testing.md — Percy, Chromatic, Applitools, BackstopJS, Lost Pixel, reg-suit; visual testing best practices; BrowserStack, Sauce Labs, LambdaTest setup
references/pom-accessibility-flaky-tests.md — Page Object Model with TypeScript, playwright-axe and cypress-axe integration, WCAG assertions, flaky test detection and quarantine workflow, test data patterns