qa-web-e2e
Web E2E testing with Playwright, Cypress, Selenium and WebdriverIO, plus cloud grids, a self-hosted Selenium Grid 4, and cross-browser test matrices. Covers BrowserStack, Sauce Labs and LambdaTest, traffic-based T1/T2/T3 browser tiers, a framework decision guide, and Playwright's agent tooling (playwright-cli, Playwright MCP, planner/generator/healer Test Agents). Agents (playwright-codegen-reviewer, automation-harness-bootstrapper) refactor recorded Playwright or Cypress Studio specs and scaffold a full E2E harness for a repo with no suite.
/plugin install qa-web-e2e@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Functional testing
- Version
v1.13.0- Contents
- 9 skills · 2 agents
Skills9
browser-matrix-strategy-referenceUse when deciding which browsers, OS versions and devices to test: a three-tier matrix built from traffic data, quarterly re-tier reviews, a published support policy and test budget, or the case for dropping an old browser.skillcloud-grid-e2eUse when E2E tests must run on real browsers and devices in BrowserStack Automate, Sauce Labs or LambdaTest: credentials, the WebDriver hub URL and vendor capabilities, a local tunnel for internal apps, session status reporting and a CI matrix sized to the plan's parallel sessions.skillcypress-testingUse whenever a project writes, fixes or upgrades Cypress E2E tests: cypress.config.ts, replacing cy.wait sleeps with assertions, cy.intercept network stubs, fixtures and cy.task, cy.clock, cy.origin logins, cy.session commands, the Cypress 16 upgrade, and Cloud parallel runs.skillplaywright-agentsUse when a coding agent works with Playwright through playwright-cli, Playwright MCP or the planner, generator and healer Test Agents: setting them up, reviewing healer diffs before merging, debugging a failing test from its trace in a terminal with no display, and leaving a video receipt.skillplaywright-testingUse whenever the task is to write, fix or speed up Playwright tests, even one quick test or a flaky one: role-based locators, web-first assertions instead of waitForTimeout, page objects, config and browser projects, traces, sharding and CI.skillselenium-grid-4-runnerUse when cross-browser tests must run on a self-hosted Selenium Grid 4 for data residency or cost: standalone or hub-and-node, the Docker images, node registration, session queue tuning and observability.skillselenium-testingUse when a project is already on Selenium WebDriver and needs tests written, fixed or upgraded in Java, Python, C# or other bindings: Selenium Manager drivers, locators, explicit waits, page objects, BiDi console errors, Grid in Docker, JUnit XML.skillweb-e2e-overviewUse when a web app has no E2E tests yet, a team is choosing or replacing an E2E framework, or a first browser test must go green.skillwebdriverio-testingUse when a team needs WebdriverIO E2E tests: npm init wdio scaffolding, services for Sauce Labs, BrowserStack, Appium and DevTools, spec, Allure and JUnit reporters, and Mocha, Jasmine or Cucumber, combining the WebDriver protocol with a plugin ecosystem.skill
Agents2
automation-harness-bootstrapperScaffolds 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.agentplaywright-codegen-reviewerAdversarial reviewer that takes raw recorded E2E specs - Playwright codegen output OR Cypress Studio recordings - and refactors them to team-ready idiomatic code.agent
About 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 skill covers Playwright's agent tooling (CLI, MCP, Test Agents), one agent scaffolds a from-zero harness skeleton, and one agent reviews raw codegen recordings (Playwright codegen + Cypress Studio).
Related reading
- Playwright 1.65 Changes How Page Object Fields Initialize
- Which Test Data Isolation Strategy Fits a Shared Database?
- Playwright Test Agents: Run the Healer Without Losing CI Signal
- Playwright Visual Tests That Pass in CI for the Right Reasons
- Playwright in GitHub Actions: Docker, Failure Capture, and Worker Parallelism
- Flaky Playwright Tests: Five Root Causes and Fixes
- How to Run Automated Tests in GitHub Actions
- Playwright vs Cypress vs Selenium: 2026 Edition
- Setting Up Playwright with TypeScript from Scratch