playwright-best-practices
npx skills add https://github.com/currents-dev/playwright-best-practices-skill --skill playwright-best-practices
Agent 安装分布
Skill 文档
Playwright Best Practices
This skill provides comprehensive guidance for all aspects of Playwright test development, from writing new tests to debugging and maintaining existing test suites.
Activity-Based Reference Guide
Consult these references based on what you’re doing:
Writing New Tests
When to use: Creating new test files, writing test cases, implementing test scenarios
| Activity | Reference Files |
|---|---|
| Writing E2E tests | test-organization.md, locators.md, assertions-waiting.md |
| Writing component tests | component-testing.md, test-organization.md |
| Writing API tests | test-organization.md, assertions-waiting.md |
| Writing visual regression tests | test-organization.md, canvas-webgl.md |
| Structuring test code with POM | page-object-model.md, test-organization.md |
| Setting up test data/fixtures | fixtures-hooks.md, test-data.md |
| Handling authentication | fixtures-hooks.md, third-party.md |
| Testing date/time features | clock-mocking.md |
| Testing file upload/download | file-operations.md |
| Testing accessibility | accessibility.md |
| Testing security (XSS, CSRF) | security-testing.md |
| Using test annotations | annotations.md |
| Testing iframes | iframes.md |
| Testing canvas/WebGL | canvas-webgl.md |
| Internationalization (i18n) | i18n.md |
| Testing Electron apps | electron.md |
| Testing browser extensions | browser-extensions.md |
Mobile & Responsive Testing
When to use: Testing mobile devices, touch interactions, responsive layouts
| Activity | Reference Files |
|---|---|
| Device emulation | mobile-testing.md |
| Touch gestures (swipe, tap) | mobile-testing.md |
| Viewport/breakpoint testing | mobile-testing.md |
| Mobile-specific UI | mobile-testing.md, locators.md |
Real-Time & Browser APIs
When to use: Testing WebSockets, geolocation, permissions, multi-tab flows
| Activity | Reference Files |
|---|---|
| WebSocket/real-time testing | websockets.md |
| Geolocation mocking | browser-apis.md |
| Permission handling | browser-apis.md |
| Clipboard testing | browser-apis.md |
| Camera/microphone mocking | browser-apis.md |
| Multi-tab/popup flows | multi-context.md |
| OAuth popup handling | third-party.md, multi-context.md |
Debugging & Troubleshooting
When to use: Test failures, element not found, timeouts, unexpected behavior
| Activity | Reference Files |
|---|---|
| Debugging test failures | debugging.md, assertions-waiting.md |
| Fixing flaky tests | flaky-tests.md, debugging.md, assertions-waiting.md |
| Debugging flaky parallel runs | flaky-tests.md, performance.md, fixtures-hooks.md |
| Ensuring test isolation / avoiding state leak | flaky-tests.md, fixtures-hooks.md, performance.md |
| Fixing selector issues | locators.md, debugging.md |
| Investigating timeout issues | assertions-waiting.md, debugging.md |
| Using trace viewer | debugging.md |
| Debugging race conditions | flaky-tests.md, debugging.md, assertions-waiting.md |
| Debugging console/JS errors | console-errors.md, debugging.md |
Error & Edge Case Testing
When to use: Testing error states, offline mode, network failures, validation
| Activity | Reference Files |
|---|---|
| Error boundary testing | error-testing.md |
| Network failure simulation | error-testing.md, network-advanced.md |
| Offline mode testing | error-testing.md, service-workers.md |
| Service worker testing | service-workers.md |
| Loading state testing | error-testing.md |
| Form validation testing | error-testing.md |
Multi-User & Collaboration Testing
When to use: Testing features involving multiple users, roles, or real-time collaboration
| Activity | Reference Files |
|---|---|
| Multiple users in one test | multi-user.md |
| Real-time collaboration | multi-user.md, websockets.md |
| Role-based access testing | multi-user.md |
| Concurrent action testing | multi-user.md |
Refactoring & Maintenance
When to use: Improving existing tests, code review, reducing duplication
| Activity | Reference Files |
|---|---|
| Refactoring to Page Object Model | page-object-model.md, test-organization.md |
| Improving test organization | test-organization.md, page-object-model.md |
| Extracting common setup/teardown | fixtures-hooks.md |
| Replacing brittle selectors | locators.md |
| Removing explicit waits | assertions-waiting.md |
| Creating test data factories | test-data.md |
Infrastructure & Configuration
When to use: Setting up projects, configuring CI/CD, optimizing performance
| Activity | Reference Files |
|---|---|
| Configuring Playwright project | test-organization.md, projects-dependencies.md |
| Setting up CI/CD pipelines | ci-cd.md, performance.md |
| Global setup & teardown | global-setup.md |
| Project dependencies | projects-dependencies.md |
| Optimizing test performance | performance.md, test-organization.md |
| Configuring parallel execution | performance.md |
| Isolating test data between workers | fixtures-hooks.md, performance.md |
| Test coverage | test-coverage.md |
Advanced Patterns
When to use: Complex scenarios, API mocking, network interception
| Activity | Reference Files |
|---|---|
| Mocking API responses | test-organization.md, network-advanced.md |
| Network interception | network-advanced.md, assertions-waiting.md |
| GraphQL mocking | network-advanced.md |
| HAR recording/playback | network-advanced.md |
| Custom fixtures | fixtures-hooks.md |
| Advanced waiting strategies | assertions-waiting.md |
| OAuth/SSO mocking | third-party.md, multi-context.md |
| Payment gateway mocking | third-party.md |
| Email/SMS verification mocking | third-party.md |
| Failing on console errors | console-errors.md |
| Security testing (XSS, CSRF) | security-testing.md |
| Performance budgets & Web Vitals | performance-testing.md |
| Lighthouse integration | performance-testing.md |
| Test annotations (skip, fixme) | annotations.md |
| Test steps for reporting | annotations.md |
Quick Decision Tree
What are you doing?
â
ââ Writing a new test?
â ââ E2E test â test-organization.md, locators.md, assertions-waiting.md
â ââ Component test â component-testing.md
â ââ API test â test-organization.md, assertions-waiting.md
â ââ Visual/canvas test â canvas-webgl.md, test-organization.md
â ââ Accessibility test â accessibility.md
â ââ Mobile/responsive test â mobile-testing.md
â ââ i18n/locale test â i18n.md
â ââ Electron app test â electron.md
â ââ Browser extension test â browser-extensions.md
â ââ Multi-user test â multi-user.md
â
ââ Testing specific features?
â ââ File upload/download â file-operations.md
â ââ Date/time dependent â clock-mocking.md
â ââ WebSocket/real-time â websockets.md
â ââ Geolocation/permissions â browser-apis.md
â ââ OAuth/SSO mocking â third-party.md, multi-context.md
â ââ Payments/email/SMS â third-party.md
â ââ iFrames â iframes.md
â ââ Canvas/WebGL/charts â canvas-webgl.md
â ââ Service workers/PWA â service-workers.md
â ââ i18n/localization â i18n.md
â ââ Security (XSS, CSRF) â security-testing.md
â ââ Performance/Web Vitals â performance-testing.md
â
ââ Test is failing/flaky?
â ââ Flaky test investigation â flaky-tests.md
â ââ Element not found â locators.md, debugging.md
â ââ Timeout issues â assertions-waiting.md, debugging.md
â ââ Race conditions â flaky-tests.md, debugging.md
â ââ Flaky only with multiple workers â flaky-tests.md, performance.md
â ââ State leak / isolation â flaky-tests.md, fixtures-hooks.md
â ââ Console/JS errors â console-errors.md, debugging.md
â ââ General debugging â debugging.md
â
ââ Testing error scenarios?
â ââ Network failures â error-testing.md, network-advanced.md
â ââ Offline (unexpected) â error-testing.md
â ââ Offline-first/PWA â service-workers.md
â ââ Error boundaries â error-testing.md
â ââ Form validation â error-testing.md
â
ââ Refactoring existing code?
â ââ Implementing POM â page-object-model.md
â ââ Improving selectors â locators.md
â ââ Extracting fixtures â fixtures-hooks.md
â ââ Creating data factories â test-data.md
â
ââ Setting up infrastructure?
â ââ CI/CD â ci-cd.md
â ââ Global setup/teardown â global-setup.md
â ââ Project dependencies â projects-dependencies.md
â ââ Test performance â performance.md
â ââ Test coverage â test-coverage.md
â ââ Project config â test-organization.md, projects-dependencies.md
â
ââ Organizing tests?
ââ Skip/fixme/slow tests â annotations.md
ââ Test steps â annotations.md
ââ Conditional execution â annotations.md
Test Validation Loop
After writing or modifying tests:
- Run tests:
npx playwright test --reporter=list - If tests fail:
- Review error output and trace (
npx playwright show-trace) - Fix locators, waits, or assertions
- Re-run tests
- Review error output and trace (
- Only proceed when all tests pass
- Run multiple times for critical tests:
npx playwright test --repeat-each=5