pymodel/react-frontend-skills

playwright

Playwright testing best practices for Next.js applications (formerly test-playwright).

Trending #9262 First seen Jun 21, 2026

Installation

$ npx skills add pymodel/react-frontend-skills --skill playwright

Summary

  • Playwright testing best practices for Next.js applications (formerly test-playwright).
  • This skill should be used when writing, reviewing, or debugging E2E tests with Playwright.
  • Triggers on tasks involving test selectors, flaky tests, authentication state, API mocking, hydration testing, parallel execution, CI configuration, or debugging test failures.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pymodel/react-frontend-skills · top by installs.

npx skills add pymodel/react-frontend-skills

Browse all from pymodel/react-frontend-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,516 B
  • docs SUMMARY.md 372 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 120 installs

SKILL.md

Playwright + Next.js Testing Best Practices

Comprehensive testing optimization guide for Playwright with Next.js applications. Contains 43 rules across 8 categories, prioritized by impact to guide reliable, fast, and maintainable E2E tests.

When to Apply

Reference these guidelines when:

  • Writing new Playwright tests for Next.js apps
  • Debugging flaky or failing tests
  • Optimizing test execution speed
  • Setting up authentication state reuse
  • Configuring CI/CD pipelines for testing
  • Testing Server Components and App Router features
  • Reviewing test code for reliability issues

Rule Categories by Priority

Priority Category Impact Prefix
1 Test Architecture CRITICAL arch-
2 Selectors & Locators CRITICAL loc-
3 Waiting & Assertions HIGH wait-
4 Authentication & State HIGH auth-
5 Mocking & Network MEDIUM-HIGH mock-
6 Next.js Integration MEDIUM next-
7 Performance & Speed MEDIUM perf-
8 Debugging & CI LOW-MEDIUM debug-

Quick Reference

1. Test Architecture (CRITICAL)

  • [arch-test-isolation](references/arch-test-isolation.md) - Use fresh browser context for each test
  • [arch-parallel-execution](references/arch-parallel-execution.md) - Enable parallel test execution
  • [arch-page-object-model](references/arch-page-object-model.md) - Use Page Object Model for complex pages
  • [arch-fixtures](references/arch-fixtures.md) - Use fixtures for shared setup
  • [arch-test-production](references/arch-test-production.md) - Test against production builds
  • [arch-cleanup-state](references/arch-cleanup-state.md) - Clean up test state after each test

2. Selectors & Locators (CRITICAL)

  • [loc-role-selectors](references/loc-role-selectors.md) - Use role-based selectors over CSS
  • [loc-data-testid](references/loc-data-testid.md) - Use data-testid for dynamic elements
  • [loc-label-selectors](references/loc-label-selectors.md) - Use getByLabel for form inputs
  • [loc-text-selectors](references/loc-text-selectors.md) - Use getByText for static content
  • [loc-avoid-xpath](references/loc-avoid-xpath.md) - Avoid XPath selectors
  • [loc-chained-locators](references/loc-chained-locators.md) - Chain locators for specificity
  • [loc-placeholder-selector](references/loc-placeholder-selector.md) - Use getByPlaceholder sparingly

3. Waiting & Assertions (HIGH)

  • [wait-web-first-assertions](references/wait-web-first-assertions.md) - Use web-first assertions
  • [wait-avoid-hard-waits](references/wait-avoid-hard-waits.md) - Avoid hard waits
  • [wait-network-idle](references/wait-network-idle.md) - Wait for observable readiness, not network idle
  • [wait-action-retries](references/wait-action-retries.md) - Let actions auto-wait before interacting
  • [wait-soft-assertions](references/wait-soft-assertions.md) - Use soft assertions for non-critical checks
  • [wait-custom-timeout](references/wait-custom-timeout.md) - Configure timeouts appropriately

4. Authentication & State (HIGH)

  • [auth-storage-state](references/auth-storage-state.md) - Reuse authentication with storage state
  • [auth-multiple-roles](references/auth-multiple-roles.md) - Use separate storage states for different roles
  • [auth-session-storage](references/auth-session-storage.md) - Handle session storage for auth
  • [auth-api-login](references/auth-api-login.md) - Use API login for faster auth setup
  • [auth-parallel-workers](references/auth-parallel-workers.md) - Use worker-scoped auth for parallel tests

5. Mocking & Network (MEDIUM-HIGH)

  • [mock-api-responses](references/mock-api-responses.md) - Mock API responses for deterministic tests
  • [mock-intercept-modify](references/mock-intercept-modify.md) - Intercept and modify real responses
  • [mock-har-files](references/mock-har-files.md) - Use HAR files for complex mock scenarios
  • [mock-abort-requests](references/mock-abort-requests.md) - Abort unnecessary requests
  • [mock-network-conditions](references/mock-network-conditions.md) - Simulate network conditions

6. Next.js Integration (MEDIUM)

  • [next-wait-hydration](references/next-wait-hydration.md) - Wait for hydration before interacting
  • [next-server-components](references/next-server-components.md) - Test server components correctly
  • [next-app-router-navigation](references/next-app-router-navigation.md) - Test App Router navigation patterns
  • [next-server-actions](references/next-server-actions.md) - Test server actions end-to-end
  • [next-baseurl-config](references/next-baseurl-config.md) - Configure baseURL for clean navigation

7. Performance & Speed (MEDIUM)

  • [perf-sharding](references/perf-sharding.md) - Use sharding for large test suites
  • [perf-headless-ci](references/perf-headless-ci.md) - Use headless mode in CI
  • [perf-browser-selection](references/perf-browser-selection.md) - Select browsers strategically
  • [perf-reuse-server](references/perf-reuse-server.md) - Reuse a matching local server when safe
  • [perf-retries](references/perf-retries.md) - Use retries to detect and diagnose flakiness

8. Debugging & CI (LOW-MEDIUM)

  • [debug-trace-viewer](references/debug-trace-viewer.md) - Use trace viewer for failed tests
  • [debug-screenshots-videos](references/debug-screenshots-videos.md) - Capture screenshots and videos on failure
  • [debug-inspector](references/debug-inspector.md) - Use Playwright Inspector for interactive debugging
  • [debug-ci-reporters](references/debug-ci-reporters.md) - Configure reporters for CI integration

How to Use

Read individual reference files for detailed explanations and code examples:

  • [Section definitions](references/_sections.md) - Category structure and impact levels

Reference Files

File Description
[AGENTS.md](AGENTS.md) Complete compiled guide with all rules
[references/sections.md](references/sections.md) Category definitions and ordering
[metadata.json](metadata.json) Version and reference information