Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vasilyu1983 avatar

Qa Testing Playwright

  • 539 installs
  • 73 repo stars
  • Updated July 13, 2026
  • vasilyu1983/ai-agents-public

qa-testing-playwright is an agent skill that runs reliable Playwright end-to-end browser tests from AI coding sessions for developers who need automated UI validation before release.

About

qa-testing-playwright is a skills.sh-listed agent skill from vasilyu1983/ai-agents-public with 456 installs and rank 6 on the catalog. It equips AI coding agents to author and run Playwright end-to-end browser tests directly from the development environment. Developers reach for qa-testing-playwright when they need repeatable UI flows exercised in real browsers instead of manual click-through checks. The skill targets reliable E2E coverage for web applications and extensions where regressions are costly. It fits the ship phase when teams want agent-assisted test creation, execution, and debugging of browser automation suites.

  • Automates browser-based end-to-end testing using Playwright
  • Enables AI agents to generate, run, and debug UI interaction tests
  • Supports headless, headed, and cloud execution modes
  • Integrates directly with Claude Code, Cursor, and similar agents
  • Produces test reports and failure screenshots automatically

Qa Testing Playwright by the numbers

  • 539 all-time installs (skills.sh)
  • +9 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #609 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/vasilyu1983/ai-agents-public --skill qa-testing-playwright

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs539
repo stars73
Last updatedJuly 13, 2026
Repositoryvasilyu1983/ai-agents-public

How do you run Playwright E2E tests from an AI agent?

Run reliable end-to-end browser tests with Playwright directly from their AI coding agent.

Who is it for?

Developers shipping web apps who want agent-assisted Playwright E2E coverage without context-switching to a separate QA toolchain.

Skip if: Backend-only services with no browser UI where unit or API contract tests are sufficient.

When should I use this skill?

The user asks to add, run, debug, or stabilize Playwright end-to-end browser tests from an AI coding session.

What you get

Playwright test files, executed E2E browser runs, and pass-or-fail results for UI flows.

  • Playwright test specs
  • E2E test run results

By the numbers

  • 456 installs on skills.sh
  • Rank 6 on the skills.sh catalog

Files

SKILL.mdMarkdownGitHub ↗

QA Testing (Playwright)

High-signal, cost-aware E2E testing for web applications.

Core docs:

  • https://playwright.dev/docs/best-practices
  • https://playwright.dev/docs/locators
  • https://playwright.dev/docs/test-retries
  • https://playwright.dev/docs/trace-viewer
  • https://playwright.dev/docs/test-sharding
  • https://playwright.dev/docs/ci

Defaults (2026)

  • Keep E2E thin: protect critical user journeys only; push coverage down (unit/integration/contract).
  • Locator priority: getByRolegetByLabel/getByTextgetByTestId (fallback).
  • Waiting: rely on Playwright auto-wait + web-first assertions; no sleeps/time-based waits.
  • Isolation: tests must run alone, in parallel, and in any order; eliminate shared mutable state.
  • Flake posture: retries are a debugging tool; treat rerun-pass as a failure signal and fix root cause.
  • CI posture: smoke gate on PRs; shard/parallelize regression on schedule; always keep artifacts (trace/video/screenshot).

Quick Start

CommandPurpose
npm init playwright@latestInitialize Playwright
npx playwright testRun all tests
npx playwright test --grep @smokeRun smoke tests
npx playwright test --project=chromiumRun a single project
npx playwright test --uiDebug with UI mode
npx playwright test --debugStep through a test
npx playwright show-trace trace.zipInspect trace artifacts
npx playwright show-reportInspect HTML report

When to Use

  • E2E tests for web applications
  • Test user authentication flows
  • Verify form submissions
  • Test responsive designs
  • Automate browser interactions
  • Set up Playwright in CI/CD

When NOT to Use

ScenarioUse Instead
Unit testingJest, Vitest, pytest
API contractsqa-api-testing-contracts
Load testingk6, Locust, Artillery
Mobile nativeAppium

Authoring Rules

Locator Strategy

// 1. Role locators (preferred)
await page.getByRole('button', { name: 'Sign in' }).click();

// 2. Label/text locators
await page.getByLabel('Email').fill('user@example.com');

// 3. Test IDs (fallback)
await page.getByTestId('user-avatar').click();

Flake Control

  • Avoid sleeps; use Playwright auto-wait
  • Use retries as signal, not a crutch
  • Capture trace/screenshot/video on failure
  • Prefer user-like interactions; avoid force: true

Workflow

  • Write the smallest test that proves the user outcome (intent + oracle).
  • Stabilize locators and assertions before adding more steps.
  • Make state explicit: seed per test/worker, clean up deterministically, mock third-party boundaries.
  • In CI: shard/parallelize, capture artifacts, and fail fast on rerun-pass flakes.

Debugging Checklist

If something is flaky:

  • Open trace first; identify whether it is selector ambiguity, missing wait, or state leakage.
  • Replace brittle selectors with semantic locators; replace sleeps with expect(...) or a targeted wait.
  • Reduce global timeouts; add scoped timeouts only when the product truly needs it.
  • If it only fails in CI, look for concurrency, cold-start, CPU starvation, and environment differences.

Do / Avoid

  • Make tests independent and deterministic
  • Use network mocking for third-party deps
  • Run smoke E2E on PRs; full regression on schedule
  • "Test everything E2E" as default
  • Weakening assertions to "fix" flakes
  • Auto-healing that weakens assertions

Execution Preflight (High ROI)

Run this preflight before expensive E2E runs to prevent avoidable failures.

Preflight Checklist

1. Repository shape:

  • Confirm working directory and expected app root exist.
  • Verify spec paths before execution (rg --files tests/e2e | rg <target>).

2. Port/process hygiene:

  • Check and clear stale dev server port before run (example: lsof -i :3001).
  • Avoid parallel local servers colliding with Playwright webServer.

3. Command validity:

  • Validate CLI flags for current tool versions before batch runs.
  • Prefer exact spec paths or --grep over broad globs during triage.

4. Artifact expectations:

  • Confirm result artifact paths exist before reading (test -f <error-context.md>).
  • If artifact path missing, inspect latest test-results index first.

Mandatory Sandbox/Port Decisions

Before running Playwright in constrained environments (sandboxed terminals, CI containers, shared dev hosts), decide and document:

  • Bind host/port: confirm whether app server must use 127.0.0.1 or 0.0.0.0, and verify selected port is free.
  • Escalation path: if bind attempts fail with EPERM/EACCES, escalate immediately instead of retry loops.
  • Long-flow timeout budget: set explicit per-test timeout for API-heavy flows (generation/checkout/report) instead of inflating global timeout.
  • Build lock hygiene: clear stale .next/lock and terminate stale build/dev PIDs before rerun.

Triage Sequence (Fastest Signal)

1. Reproduce one failing test with --workers=1. 2. Capture trace/video/screenshot for that single failure. 3. Fix determinism root cause. 4. Re-run targeted suite. 5. Only then run broad regression.

Failure Patterns to Treat as Environment, Not Product Bugs

  • EADDRINUSE on Playwright web server port
  • Missing spec/result paths from stale assumptions
  • Shell glob expansion failures for bracketed route segments

Resources

ResourcePurpose
references/playwright-mcp.mdMCP & AI testing
references/playwright-patterns.mdAdvanced patterns
references/playwright-ci.mdCI configurations
references/playwright-authentication.mdAuth patterns and session management
references/visual-regression-testing.mdVisual regression strategies
references/api-testing-playwright.mdAPI testing with APIRequestContext
references/playwright-preflight-sandbox.mdSandbox/port preflight and escalation decisions
data/sources.jsonDocumentation links

Templates

TemplatePurpose
assets/template-playwright-e2e-review-checklist.mdE2E review checklist
assets/template-playwright-fail-on-flaky-reporter.jsFail CI on rerun-pass flakes
assets/template-playwright-preflight-checklist.mdPreflight checklist for port/sandbox/timeouts

Related Skills

SkillPurpose
qa-testing-strategyOverall test strategy
software-frontendFrontend development
ops-devops-platformCI/CD integration

Fact-Checking

  • Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final answers.
  • Prefer primary sources; report source links and dates for volatile information.
  • If web access is unavailable, state the limitation and mark guidance as unverified.

Related skills

How it compares

Choose this over generic test-writing prompts when the goal is Playwright-specific E2E browser automation executed inside the agent session.

FAQ

What does qa-testing-playwright automate?

qa-testing-playwright automates end-to-end browser testing with Playwright from AI coding agent sessions. Developers use it to create and run UI flow tests in real browsers, catching regressions before release without leaving the agent workflow.

How popular is qa-testing-playwright on skills.sh?

qa-testing-playwright from vasilyu1983/ai-agents-public shows 456 installs and rank 6 on skills.sh. That catalog placement reflects strong adoption among developers running Playwright E2E tests through agent tooling.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.