Skill

role-aqa:e2e-testing

Automates end-to-end testing with Playwright (codegen, fixtures, sharding, visual comparisons), Cypress v13, Selenium 4, WebdriverIO, TestCafe. Covers visual regression (Percy, Chromatic), cross-browser (BrowserStack, Sauce Labs), accessibility.

Playwright

Cypress

testing

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

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/role-aqa:e2e-testing

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlobBash

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

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

Supporting Files

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

SKILL.md

34 lines · ~613 tokens

Similar Skills

e2e

Implements browser-based E2E tests with Playwright, Cypress, or Selenium. Covers page object models, flaky test fixes, cross-browser testing, and test architecture.

godmode

E2E Testing Patterns

faos-tea

e2e-testing

Configures and writes end-to-end tests with Playwright or Cypress for validating user flows, browser integration, CI E2E tests, acceptance tests, and production smoke tests.

alfred-dev

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceGood

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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

role-aqa:e2e-testing

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

role-aqa:e2e-testing

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

E2E Testing

When to use

Core principles

Reference Files

Similar Skills

Help us improve

E2E Testing

When to use

Core principles

Reference Files