Playwright Browser Runner
Guide browser test execution with Playwright or a similar runner as a run plan the user carries out.
Sample result
How it works
What Playwright Browser Runner does
Covers pre-flight checks, run modes (smoke, targeted, full, cross-browser, repeat for flake detection), command templates, evidence settings (trace, screenshot, video), a failure triage decision tree that separates product bugs from locator, data, environment, and flaky causes, repeat sizing, quarantine rules, and a stable run record for reporting.
Use it when
Someone asks how to run browser tests, capture evidence, triage Playwright failures, find flaky tests, or report a browser test run reliably.
Use something else for
The overall test strategy, the release verdict, accessibility checks, or writing issue text.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Browser run plan, command templates, failure triage guide and run record
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Playwright Browser Runner
Updated Oct 20, 2026.
What does Playwright Browser Runner do?
Guide browser test execution with Playwright or a similar runner as a run plan the user carries out. Covers pre-flight checks, run modes (smoke, targeted, full, cross-browser, repeat for flake detection), command templates, evidence settings (trace, screenshot, video), a failure triage decision tree that separates product bugs from locator, data, environment, and flaky causes, repeat sizing, quarantine rules, and a stable run record for reporting. Use when someone asks how to run browser tests, capture evidence, triage Playwright failures, find flaky tests, or report a browser test run reliably. Do not use for the overall test strategy (use test-plan), the release verdict (use release-regression-report), accessibility checks (use accessibility-qa), or writing issue text (use jira-evidence-uploader).
Who is Playwright Browser Runner for?
It is designed for QA engineers, test automation developers, release managers and engineering leads.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Playwright Browser Runner produce?
Browser run plan, command templates, failure triage guide and run record. Results come back with their sources and any open questions for you to check before anything is used.
How much does Playwright Browser Runner cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt9brv007n…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Playwright Browser Runner fits
Similar skills5
Accessibility Qa
Plan and report accessibility QA for a web or app experience against WCAG 2.2 level AA. Defines scope and a page and flow sample, combines automated scans with manual keyboard, screen reader, zoom and reflow, contrast, semantics, and form-error testing, computes contrast ratios, logs each issue with the success criterion, affected users, severity, and a fix direction, and ends with retest criteria. Use when someone asks for accessibility testing, an accessibility audit plan or report, keyboard or screen reader checks, contrast checks, or WCAG review of a page or flow. Do not use for the overall test plan (use test-plan), the release verdict (use release-regression-report), visual design critique (use design-audit), or posting issue text (use jira-evidence-uploader).FreeSkill · Product and engineeringdiagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.FreeSkill · Product and engineeringgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.FreeCommunitySkill · Product and engineeringJira Evidence Uploader
Package QA findings into Jira-ready drafts without posting anything. Normalizes each finding to one defect, decides new issue versus comment versus link, writes the summary, preconditions, numbered reproduction steps, expected and actual results, severity proposal, and environment block, selects and names screenshots, recordings, and log excerpts, runs a redaction check for personal data, builds an attachment manifest with hashes, and drafts new-issue, evidence, and retest comments. Use when someone asks to write up a bug for Jira, turn QA findings into tickets, package screenshots and reproduction steps, or draft evidence comments. Do not use for writing epics or stories (use jira-epic-writer), the release verdict (use release-regression-report), test planning (use test-plan), or running the tests (use playwright-browser-runner).FreeSkill · Product and engineeringRelease Regression Report
Produce a release regression report from the user's test results and defect list for one release candidate. Separates executed from planned work, computes execution, pass, and effective pass rates by priority and area, classifies every failure (regression, known issue, flaky, environment, test defect), maps failures and unexecuted tests to changed areas, rates residual risk, and ends with a go, conditional go, or no-go recommendation tied to stated gates and named waivers. Use when someone asks for a regression summary, release readiness report, go or no-go recommendation, or whether a build is safe to ship. Do not use for writing the test plan or its exit criteria (use test-plan), accessibility findings (use accessibility-qa), or turning findings into issue text (use jira-evidence-uploader).FreeHave a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.