AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Playwright Testing

skill-arozumenko-sdlc-skills-playwright-testing · by arozumenko

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
— No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-arozumenko-sdlc-skills-playwright-testing

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ● Network access Used
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Playwright Testing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Playwright Testing

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

Core Workflow

Use the Playwright MCP. The loop for any check:

  1. Navigate to the URL.
  2. Snapshot the page first (accessibility tree + element refs) — you need the refs before you can act, and the role/name pairs are what you assert on.
  3. Interact: click, type, fill a form, select an option, press a key, hover.
  4. Wait for the expected condition (an element appears, navigation completes).
  5. Re-snapshot, then collect evidence: screenshot, console messages, network requests.

Call these through the MCP — exact tool names track your installed @playwright/mcp version, so discover them from the MCP rather than hard-coding signatures here.

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Web & Browser