playwright-testing
Use when a manual-QA agent does live browser testing through the Playwright MCP server — exploring/profiling a web app or executing a web test case against a running app, with no test code generated. Web/PWA/hybrid targets; used by app-profiler and test-runner. Mobile native → use mobile-testing instead.
arozumenko · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add arozumenko/sdlc-skills --skill playwright-testingAbout this skill
name: playwright-testing description: Use when a manual-QA agent does live browser testing through the Playwright MCP server — exploring/profiling a web app or executing a web test case against a running app, with no test code generated. Web/PWA/hybrid targets; used by app-profiler and test-runner. Mobile native → use mobile-testing instead. license: Apache-2.0 compatibility: Requires Node.js 18+. Playwright MCP server (@playwright/mcp) installed via setup.yaml. metadata: authors: - Artem Rozumenko artem_rozumenko@epam.com version: "0.3.0"
Playwright Testing (live, via MCP)
Live browser testing for the manual-QA team. You drive a real browser through
the Playwright MCP server (@playwright/mcp) to explore a web app or execute a
test case step-by-step against a running app. You never write or run Playwright
test code — no Page Object Model, no pytest, no .spec.ts files. The output is
a verdict plus evidence, not a test suite.
Writing actual Playwright test code is
test-automation-engineer's job (a different factory's copy of this skill). Here, the browser is your hands.
When to use
app-profiler— explore a running web app: map key flows, capture reliable selectors and fragile areas intoapp_profile.md.test-runner— execute one webTC-NNNcase live: run each step, verify, collect evidence, return a structured result.- Web / PWA / hybrid only. Native iOS/Android → use the
mobile-testingskill. (PWA/hybrid with a mobile viewport is still this skill.)
Core loop — snapshot first
The Playwright MCP exposes browser_* tools. The loop for every check:
browser_navigate(url)— go to{{base_url}}/path(substitutebase_urlfrom the run prompt). Navigation auto-waits for load.browser_snapshot()— the accessibility snapshot gives each element atargetref plus its role and accessible name. You need the ref before you can act, and role/name is what you assert on.- Act by passing that ref as
target(plus a short human-readableelementdescription):browser_click,browser_type,browser_fill_form,browser_select_option,browser_press_key,browser_hover. browser_wait_for({text})/({textGone})— wait for the expected text to appear, or a spinner/loader text to disappear, before continuing.browser_snapshot()again, then collect evidence:browser_take_screenshot,browser_console_messages,browser_network_requests.
Refs go stale. Every target ref comes from the latest snapshot — after
any navigation or DOM change, re-browser_snapshot before acting again. The
server is versioned; this skill is written against the browser_* toolset and
parameter names can shift between @playwright/mcp releases.
MCP tool quick reference
| Tool | Key params (* = required) | Use |
|---|---|---|
browser_navigate | url* | Go to a URL |
browser_snapshot | — | Accessibility snapshot → element refs (target) + roles/names |
browser_click | element, target*, doubleClick, button | Click an element |
browser_type | element, target*, text*, submit, slowly | Type into one field (submit:true presses Enter after) |
browser_fill_form | fields* | Fill many fields in one call (see below) |
browser_select_option | element, target*, values* | Pick option(s) in a native <select> |
browser_press_key | key* | Press a key (Enter, Escape, ArrowDown, a) |
browser_hover | element, target* | Hover |
browser_wait_for | text / textGone / time | Wait for text to appear / disappear / N seconds |
browser_take_screenshot | type* (png|jpeg), filename, fullPage | Capture evidence |
browser_console_messages | level* (error|warning|info|debug) | Read console (use level:"error") |
browser_network_requests | static*, filter | List network calls |
browser_handle_dialog | accept*, promptText | Accept/dismiss a native JS dialog/alert |
browser_file_upload | paths | Upload file(s) into a file chooser |
browser_navigate_back · browser_tabs · browser_resize | — | Back · tab mgmt · viewport |
target* is the ref from the latest browser_snapshot (a unique CSS
selector also works); always pass element too — a short description of what
you're acting on.
{{base_url}} rule
All test-case URLs are written {{base_url}}/path. Substitute the real base URL
from the run prompt into the browser_navigate(url) call at execution time —
this keeps cases environment-agnostic across dev / staging / prod.
Filling a form (one call)
browser_fill_form fills every field in a single call. Each field is
{element, target, name, type, value}, where type ∈
textbox | checkbox | radio | combobox | slider (checkbox/radio value is
"true"/"false"; combobox value is the option text):
browser_snapshot() # get refs first
browser_fill_form(fields=[
{element:"Email field", target:"<ref>", name:"Email", type:"textbox", value:"qa@example.com"},
{element:"Password field", target:"<ref>", name:"Password", type:"textbox", value:"Passw0rd!"},
{element:"Remember me", target:"<ref>", name:"Remember", type:"checkbox", value:"true"},
])
For a single field, browser_type(element, target, text, submit:true) types and
presses Enter in one step.
Mapping test-case steps to MCP tools
Test cases are written in plain language. Map each step verb to a tool call:
| TC step verb | MCP tool call |
|---|---|
| Open / Go to X | browser_navigate(url:"{{base_url}}/…") |
| Click / Tap X | browser_click(element, target) |
| Enter V in field F | browser_type(element, target, text:"V") — or browser_fill_form for several |
| Select O from D | browser_select_option(element, target, values:["O"]) |
| Press K | browser_press_key(key:"K") |
| Hover over X | browser_hover(element, target) |
| Verify / See X | `brow |