skills.rest
indykish
indykishCOMMUNITY
Explore all skills by this author →
Website𝕏@indykishGitHub

e2e-qa-playwright

Automate end-to-end QA for web applications using Playwright CLI.

2|Updated Dec 8, 2018
Search Tags:#automation#testing#e2e#qa#playwright#headless#ci
One-click install
npx skills add https://github.com/indykish/dotfiles --skill e2e-qa-playwright
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-qa-playwright
Source: https://github.com/indykish/dotfiles/tree/main/skills/e2e-qa-playwright
Command: npx skills add https://github.com/indykish/dotfiles --skill e2e-qa-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end QA workflows for web applications using Playwright CLI to deliver reliable, deterministic test results in CI.

Core Features & Use Cases

  • Deterministic selectors and consistent test runs with Playwright.
  • CI-friendly execution that captures and stores screenshots, videos, and traces as artifacts.
  • Simple local debugging with headless by default and headed runs via bunx playwright test --headed when needed.

Quick Start

Run make qa to execute the full Playwright e2e suite in CI.

Frequently Asked Questions about e2e-qa-playwright

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

FAQPage Schema
How do I run Playwright e2e tests in a CI pipeline?▼

Run Playwright e2e tests in CI by executing the make qa target, which uses bunx playwright test with a Chromium-based browser in headless mode to ensure deterministic test execution and capture artifacts.

How do I run a smoke test suite with Playwright locally?▼

Run a Playwright smoke test suite locally by using the make qa-smoke target. You can debug visually by appending a headed mode flag via bunx playwright test --headed instead of the default headless execution.

How do I capture Playwright test artifacts like screenshots and traces?▼

Playwright test artifacts such as screenshots, videos, and traces are captured automatically during CI-friendly execution when you run the make qa target, storing them for post-run analysis and flaky-test reporting.

Do I need to install Playwright separately to use the make qa target?▼

Playwright is executed via bunx, which handles the package execution. You need to ensure your environment has bun installed and provide a BASE_URL for the dev server to run the e2e QA suite successfully.

Can I use a custom dev server URL for Playwright end-to-end QA?▼

Yes, you can use a custom dev server URL for Playwright end-to-end QA by setting the BASE_URL environment variable, allowing the test suite to point to your specific local development or staging environment.

Why are my Playwright e2e tests flaky in continuous integration?▼

Flaky Playwright e2e tests in CI can be identified through the Skill's flaky-test analysis and exact command output reporting, which leverages deterministic selectors and consistent headless Chromium execution to isolate non-deterministic behavior.

Related Skills

Explore More Software Engineering Skills→
LimaTechnologiesLimaTechnologies

bun-runtime

Codify Bun runtime patterns for package management, bundling, testing, and scripting workflows.

Community
Advanced
andyan77andyan77

diyu-e2e-runner

Coordinate Playwright end-to-end tests, isolate flaky tests, and collect artifacts.

Community
Advanced
emcconnellemcconnell

team-qa

Coordinate QA team execution to produce test plans, cases, bug reports, and sign-off reports.

Community
Advanced
kys0213kys0213

testing

Generate unit, Playwright E2E, or Electron E2E tests for AgentOS projects.

Community
Intermediate