qa-web-e2e
Web E2E framework wrappers + cross-browser strategy and grids: 8 skills (playwright-testing carrying the cross-browser matrix reference, cypress-testing, selenium-testing, webdriverio-testing, cloud-grid-e2e covering BrowserStack / Sauce Labs / LambdaTest, selenium-grid-4-runner for the self-hosted grid, browser-matrix-strategy-reference with the T1/T2/T3 tiering + compatibility budget + matrix review checklist, and the web-e2e-overview decision guide) and 2 agents (playwright-codegen-reviewer, which also reviews Cypress Studio recordings, and automation-harness-bootstrapper, which scaffolds a full E2E harness skeleton for a repo with no suite).
Install this plugin
/plugin install qa-web-e2e@testland-qaPart of role bundles: qa-role-automation-engineer, qa-role-sdet, qa-role-frontend
qa-web-e2e
Web E2E framework wrappers (per-framework skills). Full lifecycle per framework: author + run + traces + flake debug + CI integration. Cloud browser grids (BrowserStack / Sauce Labs / LambdaTest) live in one umbrella skill, the self-hosted Selenium Grid 4 runner and the browser-matrix strategy reference (tiering + compatibility budget + review checklist) cover cross-browser planning and execution, one agent scaffolds a from-zero harness skeleton, and one agent reviews raw codegen recordings (Playwright codegen + Cypress Studio).
Components
| Type | Name | Description |
|---|---|---|
| Skill | web-e2e-overview | Teaches web E2E testing from first principles - what browser-driven E2E covers, a repo-observation decision table for choosing between Playwright, Cypress, Selenium, WebdriverIO and the cloud grids, first-run commands per tool, and the flakiness traps that sink new suites. |
| Skill | playwright-testing | Authors Playwright E2E tests across Chromium, Firefox, WebKit - scaffolding, browser projects, accessibility-first locators, web-first assertions, Page Objects, trace viewer, sharding, mobile-web emulation via the devices catalog, CI integration. |
| Skill | cypress-testing | Authors Cypress E2E tests - npm install cypress, cypress.config.ts setup, cy.* command chains, automatic-waiting commands, time-travel debugging, custom commands, CI integration. |
| Skill | selenium-testing | Authors Selenium WebDriver tests in any of its 6+ supported languages (Java, Python, JavaScript, C#, Ruby, Kotlin, PHP) - picks the appropriate binding per project stack. |
| Skill | webdriverio-testing | Authors WebdriverIO E2E tests - npm init wdio@latest scaffolding, services architecture (sauce, browserstack, appium, devtools), reporters, CI integration. |
| Skill | cloud-grid-e2e | Author and run E2E tests on a cloud browser grid - BrowserStack Automate, Sauce Labs, or LambdaTest. One vendor-generic pattern (auth env vars, hub URL, vendor options dict, local tunnel, CI wiring) with per-vendor deltas in references/. |
| Skill | selenium-grid-4-runner | Author and operate Selenium Grid 4 - the self-hosted distributed WebDriver grid: six-component architecture, standalone vs hub-and-node modes, Docker image stack, session-queue tuning, observability. For data-residency or cost-control cases where cloud grids don't fit. |
| Skill | browser-matrix-strategy-reference | Pure reference for designing and reviewing a browser / OS / device matrix from traffic data - T1/T2/T3 tier heuristics, traffic-share sources, matrix template + tier-change log, the matrix review checklist, and the compatibility budget (tier caps, CI cost, support statement) in references/. |
| Agent | playwright-codegen-reviewer | Adversarial reviewer that takes raw recorded specs - Playwright codegen output or Cypress Studio recordings - and refactors them to team-ready idiomatic code (Page Objects / custom commands, accessibility-first selectors, retry-aware waits, AAA structure). |
| Agent | automation-harness-bootstrapper | Scaffolds a complete test-automation harness skeleton (folder layout, base fixtures, page-object base class, one smoke test, CI job) for a repo with no existing E2E infrastructure - Playwright by default, Cypress variant included. |
Install
/plugin marketplace add testland/qa
/plugin install qa-web-e2e@testland-qaSkills
browser-matrix-strategy-reference
Pure-reference for designing and reviewing a browser / OS / device test matrix from traffic data - the T1/T2/T3 tier-membership heuristics (T1 >=5% traffic, T2 1-5% or statutory, T3 <1% with customer demand), the traffic-share sources (own analytics, StatCounter, MDN browser-compat-data), a worked matrix template with tier-change log, the matrix review checklist (staleness, T1 oversize, below-threshold T1 entries, missing real-device coverage), how to justify dropping a legacy browser (IE11, old iOS Safari), and the compatibility budget (tier caps, CI cost formula, published support statement) in references/compatibility-budget.md. Use when designing an initial matrix, capping or publishing a support policy, running a quarterly re-tier review, or making the case to drop a browser. This is the WHAT-to-test strategy reference - to execute the matrix use playwright-testing browser projects (bundled engines), selenium-grid-4-runner (self-hosted), or cloud-grid-e2e (managed grids).
cloud-grid-e2e
Author and run E2E tests on a cloud browser grid - BrowserStack Automate, Sauce Labs, or LambdaTest. All three follow one pattern: username + access-key env vars, a W3C WebDriver hub URL, a vendor options dict inside the capabilities (bstack:options / sauce:options / LT:Options), a local tunnel binary for internal apps, session pass/fail reporting, and a CI matrix throttled to the plan's parallel-session limit. Worked example uses BrowserStack; per-vendor deltas live in references/. Use for cross-browser regression on real devices + browsers beyond the engines bundled on the local machine - distinct from a local matrix runner and from self-hosted Selenium Grid.
cypress-testing
Authors and improves Cypress E2E tests - installs Cypress, configures `cypress.config.ts`, authors `cy.*` command chains, refactors existing specs (`cy.wait(ms)` sleeps into assertions, repeated flows into `cy.session` custom commands), and debugs with the time-travel GUI; Cypress Cloud for parallel runs and recording. Use for both greenfield test authoring and improving hand-written specs already in the codebase. For automated refactor of raw Cypress Studio recordings specifically, use a dedicated codegen-review pass.
playwright-testing
Authors and remediates Playwright E2E tests across Chromium, Firefox, WebKit - `npm init playwright@latest` scaffolding, `playwright.config.ts` browser projects, accessibility-first locators (`getByRole`/`getByLabelText`) to replace brittle CSS selectors, web-first assertions to eliminate `waitForTimeout` flakiness, Page Object pattern, trace viewer debugging, sharded parallel execution with merged HTML reporting, mobile-web emulation via the `devices` catalog (viewport / DPR / touch per-device projects), the cross-browser matrix with branded channels (chrome / msedge) in references/browser-matrix.md, and GitHub Actions CI integration. Use for new test authoring, flakiness remediation, mobile-breakpoint regression, cross-browser matrix setup, and CI setup; for reviewing codegen output specifically, use a dedicated codegen-review pass.
selenium-grid-4-runner
Author and operate Selenium Grid 4 - self-hosted distributed WebDriver. Covers the six-component architecture (Router / Distributor / Session Map / Event Bus / New Session Queue / Node), standalone vs hub-and-node modes, the Docker-image stack (selenium/standalone-chrome, selenium/hub, selenium/node-chrome), node registration, session-queue tuning, and observability. Use for self-hosted cross-browser testing when data residency or cost-control require an on-prem grid. This is the self-hosted execution RUNNER - for the zero-infra alternative use playwright-testing browser projects (bundled engines); for managed cloud grids use cloud-grid-e2e (BrowserStack / Sauce Labs / LambdaTest); to decide WHICH browsers and tiers to run use browser-matrix-strategy-reference.
selenium-testing
Authors Selenium WebDriver tests in any of its 6+ supported languages (Java, Python, JavaScript, C#, Ruby, Kotlin, PHP) - picks the appropriate language binding, configures WebDriver per browser, uses `By.*` locators with the team's accessibility-first preference where supported, runs locally + via Selenium Grid for distributed execution, parses results to JUnit XML. Use for legacy Selenium-locked stacks; new projects pick Playwright or Cypress.
web-e2e-overview
Teaches web end-to-end testing from first principles: what browser-driven E2E covers and how it differs from unit and integration tests, a decision table for choosing between Playwright, Cypress, Selenium WebDriver, WebdriverIO, Puppeteer, TestCafe and the BrowserStack / Sauce Labs / LambdaTest cloud grids based on files already present in the repo, install and first-run commands for each, and the flakiness traps (fixed sleeps, CSS and XPath selectors, state shared between tests) that sink new suites. Use when a web application has no E2E coverage yet, when picking or replacing an E2E framework, or when a first browser test needs to go green end to end.
webdriverio-testing
Authors WebdriverIO E2E tests - `npm init wdio@latest` scaffolding, services architecture (sauce, browserstack, appium, devtools), reporters (spec, allure, junit), built-in Mocha/Jasmine/Cucumber framework integrations. WebdriverIO sits between Selenium (W3C protocol) and Playwright (modern API) - Selenium-protocol-compatible with rich plugin ecosystem. Use when the team needs WebDriver protocol + service-based device-farm integration.
Agents
automation-harness-bootstrapper
Scaffolds a test-automation framework skeleton for a repo that has none - given the app's stack and entry points, generates the folder layout, base fixtures, a page-object (or screenplay) base class, one example smoke test, and the CI job that runs it. Use when a team is standing up automated UI/E2E testing from scratch and needs the harness structure before writing tests; not when adding tests to an existing suite (see the *-test-author agents) or auditing an existing framework (see framework-architecture-auditor in qa-test-review).
playwright-codegen-reviewer
Adversarial reviewer that takes raw recorded E2E specs - Playwright codegen output OR Cypress Studio recordings - and refactors them to team-ready idiomatic code. For Playwright: extracts repeated selectors into Page Object methods, replaces brittle CSS selectors with `getByRole` accessibility-first equivalents, restructures the recorded sequence into AAA-pattern tests. For Cypress: extracts repeated login / navigation flows into custom commands, rewrites CSS/class selectors as `data-cy` / `cy.findByRole` equivalents, replaces fixed `cy.wait(ms)` sleeps with retry-aware assertions or aliased intercepts, and applies the app-action pattern (programmatic state setup instead of UI-driven flows). Use after recording a flow with `npx playwright codegen` or Cypress Studio, or when a raw recording lands in a PR.