playwright-skill

왜 쓰나요

핵심 기능

Model-invoked — Claude writes custom Playwright code tailored to your ask
Headed browser by default so you can see the automation run
Built-in run.js handles module resolution so scripts just work
On-demand Playwright API reference loading to keep the context lean
Handles testing, form filling, click-throughs, broken-link checks, responsive checks

라이브 데모

실제 사용 모습

playwright-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: playwright-skill

Write a smoke test for a signup flow on demand

👤 Developers who want a test without hand-writing Playwright ⏱ ~10 min beginner

언제 쓸까: You pushed a new signup flow and want to know it still works end-to-end.

사전 조건

Node + Playwright installable — The skill will install browsers via npx playwright install if missing

흐름

Describe the flow

Use the playwright skill. Open localhost:3000, sign up with [email protected] / Pass123!, verify we land on /dashboard.✓ 복사됨

→ Claude writes a Playwright script, runs it headed, reports pass/fail
Debug failures interactively

It failed at the email input — add a screenshot right before the error.✓ 복사됨

→ Next run captures and returns the screenshot

결과: A one-off smoke test you can optionally save as a persistent spec.

함정

Selectors chosen are brittle (e.g. nth-child) — Ask Claude to prefer role/label selectors

함께 쓰기: filesystem

Find all broken links on a documentation site

👤 Docs maintainers ⏱ ~15 min intermediate

언제 쓸까: You suspect link rot after a restructuring.

흐름

Describe the crawl

Use playwright to crawl https://docs.example.com up to depth 2, log every link, and return the 404s.✓ 복사됨

→ Claude writes a BFS crawler, runs it, outputs a list

결과: A triaged list of dead links to fix.

함정

Crawler hits the site hard — Cap concurrency at 2-3 and add small delays

Spot-check responsive rendering across 3 viewports

👤 Frontend devs validating a layout change ⏱ ~5 min beginner

언제 쓸까: You changed the header and want to see how it renders on desktop, tablet, and mobile.

흐름

Request screenshots

Use playwright to screenshot localhost:3000 at 1440, 768, and 390 width. Save them.✓ 복사됨

→ 3 PNGs saved and paths returned

결과: Three screenshots for quick visual review.

함정

Screenshots don't wait for fonts/images — Add a networkidle wait before snapping

함께 쓰기: filesystem

조합

다른 MCP와 조합해 10배 효율

playwright-skill + filesystem

Save test specs and screenshots alongside the code they test

Write the smoke test and save it under tests/e2e/signup.spec.js.✓ 복사됨

playwright-skill + github

Run the test, fail the workflow, post results on the PR

Run the playwright spec against the deploy preview, then post results as a comment on PR #42.✓ 복사됨

playwright-skill + ios-simulator-skill

Playwright for web, ios-simulator-skill for native — use both in a cross-platform test session

Run the playwright web flow and the ios-simulator native flow in sequence, report both.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
Custom Playwright script generation	task description	Any browser automation ask
run.js executor	script path	After script generation
Headed/headless toggle	flag	CI vs local debugging

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: 1-5k per test run, depending on how much Playwright reference Claude pulls in
금액: Free — you only need Node + Playwright browsers on disk
팁: Keep prompts focused; don't ask for 'test everything' in one shot.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials in the skill. If your tests hit authenticated pages, keep creds in env vars — never in the generated script.

데이터 외부 송신: Only to sites your test visits

Generated scripts run with full local-process privileges — review before running against production URLs.

문제 해결

자주 발생하는 오류와 해결

'browserType.launch: Executable doesn't exist'

Run npx playwright install chromium

확인: npx playwright --version

Selector fails intermittently

Switch to role/label selectors; add await expect(...).toBeVisible() waits.

Script hangs

Claude likely forgot to close the browser. Tell it to always wrap in try/finally with await browser.close().

대안