Skip to content
Skills Library
Programming · Testing

playwright-testing

/playwright-testing

UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.

Repository
wikis ↗
Licence
MIT
Last repository change
07.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.

Triggers from the description

test the UIautomate browser testscheck the pagetake a screenshotrun Playwrightwrite E2E tests
Original author description

UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.

How it works

  1. Core Workflow
  2. Quick Reference
  3. Testing Patterns
  4. Evidence Collection
  5. Wait Strategies
  6. Bug Report Format
  7. Details
Original SKILL.md headings · 104 lines, 365 words
SKILL.md preview
---
name: playwright-testing
description: UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.
license: Apache-2.0
compatibility: Requires Node.js 18+. MCP server installed via setup.yaml.
metadata:
  author: octobots
  version: "0.1.0"
---

# Playwright Testing

Browser-based UI and E2E testing using Playwright MCP tools.

## Core Workflow

```
browser_navigate → browser_snapshot → interact → browser_wait_for →
browser_snapshot → evidence collection
```

**Always snapshot before interacting** — you need element refs to click/type.

## Quick Reference

### Navigate & Inspect
```
browser_navigate(url)               → load page
browser_snapshot()                   → get DOM tree + element refs
browser_take_screenshot()            → visual evidence
browser_console_messages()           → JS errors, warnings
browser_network_requests()           → API calls, status codes
```

### Interact
```
browser_click(element="ref")         → click element
browser_type(element="ref", text)    → type into input
browser_fill_form(values)            → fill multiple fields
browser_select_option(element, value)→ select dropdown option
browser_press_key(key)               → keyboard action
browser_hover(element="ref")         → hover for tooltips
```

### Wait & Verify
```
browser_wait_for(selector, timeout)  → wait for element
browser_wait_for(url_pattern)        → wait for navigation
```

## Testing Patterns

### 1. Verify Page Loads
```
navigate → snapshot → verify key elements exist → screenshot
```

### 2. Form Submission
```
navigate → snapshot → fill_form → click submit →
wait_for(networkidle) → snapshot → verify success state → screenshot
```

### 3. Interactive Feature
```
navigate → snapshot → click element → wait_for change →
snapshot → verify new state → console_messages → screenshot
```

### 4. API + UI Verification
```
curl API to create data → navigate to page → snapshot →
verify data appears in UI → screenshot
```

## Evidence Collection

After every significant interaction, collect:
1. **Screenshot** — visual proof
2. **Console messages** — catch JS errors the UI hides
3. **Network requests** — verify API calls succeeded

**Check console even when the UI looks fine.** Silent errors are the worst bugs.

## Wait Strategies

| Situation | Strategy |
|-----------|----------|
| Page load | `wait_for(networkidle)` |
| Dynamic content | `wait_for(selector)` |
| Navigation | `wait_for(url_pattern)` |
| Animation | `wait_for(timeout: 1000)` — last resort |

**Never use fixed waits when a condition-based wait works.**

## Bug Report Format

When you find an issue:

```
## [SEVERITY] Title

Steps: 1. Navigate to... 2. Click... 3. Observe...
Expected: What should happen
Actual: What happens
Evidence: screenshot, console error, network response
Frequency: Always / Intermittent / Once
```

## Details

See `references/patterns.md` for Page Object Model, fixture strategies, and framework-specific selectors.
Files in this package (3)
  • SKILL.md 3 KB
  • setup.yaml 1 KB
  • references/patterns.md 4 KB

Versions

RepositoryScoreLicence
This page · arozumenko/wikis100MIT
marmelab/atomic-crm100MIT
event4u-app/agent-config100MIT
TerminalSkills/skills100Apache-2.0
arozumenko/sdlc-skills100MIT
arozumenko/sdlc-skills100MIT
laurigates/claude-plugins100MIT
aehrc/pathling100MIT
testland/qa100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version b679f67e3393 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95playwright
    Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing,…
  • 100playwright-cli
    Automate browser interactions, test web pages and work with Playwright tests using the playwright-cli command. Use when the user wants to open a browser, navigate pages, click elements, fill forms, take screenshots, run Playwright tests, debug browser automation, or perform any…
  • 95memstack-development-webapp-testing
    Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
  • 95playwright-test
    Creates Playwright browser-based end-to-end tests for Next.js pages covering complete user journeys from start to finish. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing,…
  • 100playwright-expert
    Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression…
  • 100e2e-playwright-testing
    End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, form submission testing, or user flow testing. Triggers on "playwright", "e2e test", "browser test", "end-to-end", "form flow testing", or test files in tests/e2e/.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.