playwright-qa

Execute Playwright browser passes and capture screenshots, traces, and run summaries.

11|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Arcanada-one/datarim --skill playwright-qa-arcanada-one
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-qa
Source: https://github.com/Arcanada-one/datarim/tree/main/skills/playwright-qa
Command: npx skills add https://github.com/Arcanada-one/datarim --skill playwright-qa-arcanada-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent or broken frontend changes by turning UI-affecting edits into an evidence-based browser verification pass that captures screenshots, traces, and run summaries.

Core Features & Use Cases

  • Frontend touch detection with scoped triggering: Detects HTML/CSS/JS framework changes (and markup-like PHP) via git diff --name-only and only then runs a Playwright pass.
  • Deterministic resolution chain for Playwright tooling: Chooses the execution method via DATARIM_PLAYWRIGHT override, then CLI (playwright), then MCP, then an executable pointed by environment variables, otherwise records a finding instead of failing.
  • Headed/headless modes with strict operator guardrails: Supports default headless, lenient headed with graceful fallback when no display exists, and strict headed mode that aborts when a display is missing.
  • Artifact layout with concurrency safety: Writes per-task run artifacts under datarim/qa/playwright-{ID}/ and serializes concurrent QA runs using a per-task lock file.

Quick Start

Run browser QA for the current task by invoking /dr-qa --headed-strict so the run captures Playwright artifacts and fails fast if no display is available.

Frequently Asked Questions about playwright-qa

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

FAQPage Schema
How do I automate UI regression testing for frontend changes?

Playwright browser QA validates frontend changes by executing a real browser pass and producing traceable artifacts for evidence-based QA. It detects HTML, CSS, JS, or markup-like PHP changes via git diff and captures screenshots, traces, and run summaries.

How does frontend verification handle headed mode without a display?

Frontend verification supports default headless, lenient headed with graceful fallback when no display exists, and strict headed mode that aborts when a display is missing. Strict display enforcement ensures runs fail fast if the required environment is unavailable.

Can I use Playwright QA with markup-like PHP files?

Yes, Playwright QA can be used with markup-like PHP files where a UI surface must be verified. The tool detects these changes via git diff --name-only alongside standard HTML, CSS/SCSS, and TS/JS/SPA component files to trigger a browser verification pass.

What is the best way to prevent inconsistent frontend UI changes in CI?

Preventing inconsistent frontend UI changes is achieved by serializing concurrent QA runs using a per-task lock file. This concurrency safety writes per-task run artifacts under datarim/qa/playwright-{ID}/, ensuring isolated and traceable evidence-based verification.

How do I resolve Playwright tooling when the CLI is missing?

Playwright tooling is resolved via a deterministic chain: DATARIM_PLAYWRIGHT override, then CLI, then MCP, then an executable pointed by environment variables. If none are found, it records a finding instead of failing the verification run.

Does browser QA trigger on backend-only code changes?

No, browser QA only triggers when the git diff includes HTML, CSS/SCSS, TS/JS/SPA component files, or markup-like PHP where a UI surface must be verified. Backend-only changes without UI-affecting edits do not trigger a Playwright pass.