skills.rest
FluxonLab
FluxonLabCOMMUNITY
Explore all skills by this author →
Website𝕏@fluxonlabGitHub

playwright-e2e-audit

Creates and audits Playwright E2E tests for browser flows with stable locators and web-first assertions.

2|Updated Jun 1, 2026
Search Tags:#browser automation#flaky tests#playwright#e2e testing#visual regression#cypress#web-first assertions
One-click install
npx skills add https://github.com/FluxonLab/Skillry --skill playwright-e2e-audit-fluxonlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-e2e-audit
Source: https://github.com/FluxonLab/Skillry/tree/main/plugins/testing-and-qa/skills/53-playwright-e2e-audit
Command: npx skills add https://github.com/FluxonLab/Skillry --skill playwright-e2e-audit-fluxonlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, and includes references (resource) components.

What problem does it solve? Browser-based apps often ship without verified critical user journeys, or accumulate flaky E2E suites full of broken selectors and blind waitForTimeout calls that erode confidence. This Skill creates minimal, stable Playwright coverage for the highest-value flows and repairs existing flaky suites instead of rewriting them. ## Core Features & Use Cases - Minimal E2E Spec Creation: Covers the 1 to 3 highest-value user journeys using role/text/test-id locators, web-first auto-waiting assertions, and a webServer config block that starts the local app automatically. - Flaky Suite Audit and Repair: Maps symptoms (CI-only failures, selector breakage, assertion races) to root causes and concrete fixes such as auth-state reuse via storageState. - Absorbed Reference Library: Routes to in-depth references for Cypress/Playwright patterns, Chrome DevTools MCP debugging, visual regression baselines, local webapp scripting, and API test suite review. - Use Case: After a UI refactor breaks your login and checkout specs, run this Skill to replace brittle CSS selectors with getByRole, remove waitForTimeout sleeps, wire baseURL into the config, and produce a passing run with trace artifacts for any remaining failure. ## Quick Start Audit my existing Playwright suite for flaky tests and add a minimal E2E spec covering the login and checkout flows against my local dev server.

Frequently Asked Questions about playwright-e2e-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Playwright E2E tests for a local web app?▼

Install @playwright/test, set baseURL and a webServer block in playwright.config.ts so the dev server starts automatically, then write specs using getByRole or getByTestId locators with web-first assertions like toBeVisible that auto-wait. Run headless first and re-run with --trace on to diagnose failures.

How to fix flaky Playwright tests that fail only in CI?▼

CI-only failures usually mean elements are not ready when asserted. Replace every page.waitForTimeout with a web-first assertion such as await expect(locator).toBeVisible(), isolate shared state between specs, and reuse a saved storageState for login instead of re-authenticating per test.

Playwright vs Cypress for end-to-end testing patterns?▼

Both are covered in the references: Playwright uses auto-waiting web-first assertions, route interception, and storageState auth reuse, while Cypress relies on custom commands and cy.intercept. The e2e-testing-patterns reference includes page objects, fixtures, and mocking examples for each.

Can Playwright tests reuse login state across specs?▼

Yes. Authenticate once in a setup project, save the session with context.storageState to a gitignored file, and reference it in dependent projects via the use.storageState config option. Credentials must come from environment variables for a test account, never hardcoded.

When should I not use E2E browser tests?▼

Skip E2E for unit-level logic, API-only contract checks, and edge cases that are too slow at the browser layer. Also never point E2E suites at production data, live payment flows, or real user credentials; restrict runs to local or dev URLs with fixtures.

Related Skills

Explore More Software Engineering Skills→
EveryIncEveryInc
24.7k

ce-test-browser

Runs end-to-end browser tests on routes affected by a branch or pull request.

Official
Advanced
OM-bit-hubOM-bit-hub

ci-test-pipeline

Automate CI/CD pipeline setup with parallel test runs and coverage reporting.

Community
Advanced
hduoc2003hduoc2003

guardian-validation-matrix

Selects the minimal test, build, and smoke validation set for Guardian repository changes.

Community
Intermediate
sanity-iosanity-io
6.3k

sanity-visual-regression

Adds and maintains Chromatic visual regression coverage via Storybook stories, Vitest browser tests, and Playwright snapshots.

Official
Advanced