Cross-browser E2E testing with Page Objects, authentication, and CI/CD integration.
Works with
Supports three browser engines (Chromium, Firefox, WebKit) plus mobile viewports with parallel test execution and automatic retries
Page Object Model pattern with base classes, role-based locators, and web-first assertions that auto-wait and retry
Built-in authentication setup, API mocking, visual testing, and comprehensive dead link detection across entire sites
GitHub Actions integration with art
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywright-testingExecute the skills CLI command in your project's root directory to begin installation:
Fetches playwright-testing from alinaqi/claude-bootstrap and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate playwright-testing. Access via /playwright-testing in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
570
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
570
stars
Load with: base.md + [framework].md
For end-to-end testing of web applications with Playwright - cross-browser, fast, reliable.
Sources: Playwright Best Practices | Playwright Docs | Better Stack Guide
# New project
npm init playwright@latest
# Existing project
npm install -D @playwright/test
npx playwright install
// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';
export default defineConfig({
testDir: './e2e',
fullyParallel: true,
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 2 : 0,
workers: process.env.CI ? 1 : undefined,
reporter: [
['html'],
['list'],
process.env.CI ? ['github'] : ['line'],
],
use: {
baseURL: process.env.BASE_URL || 'http://localhost:3000',
trace: 'on-first-retry',
screenshot: 'only-on-failure',
video: 'retain-on-failure',
},
projects: [
// Auth setup - runs once before all tests
{ name: 'setup', testMatch: /.*\.setup\.ts/ },
{
name: 'chromium',
use: { ...devices['Desktop Chrome'] },
dependencies: ['setup'],
},
{
name: 'firefox',
use: { ...devices['Desktop Firefox'] },
dependencies: ['setup'],
},
{
name: 'webkit',
use: { ...devices['Desktop Safari'] },
dependencies: ['setup'],
},
// Mobile viewports
{
name: 'mobile-chrome',
use: { ...devices['Pixel 5'] },
dependencies: ['setup'],
},
{
name: 'mobile-safari',
use: { ...devices['iPhone 12'] },
dependencies: ['setup'],
},
],
// Start dev server before tests
webServer: {
command: 'npm run dev',
url: 'http://localhost:3000',
reuseExistingServer: !process.env.CI,
timeout: 120 * 1000,
},
});
project/
├── e2e/
│ ├── fixtures/
│ │ ├── auth.fixture.ts # Auth fixtures
│ │ └── test.fixture.ts # Extended test with fixtures
│ ├── pages/
│ │ ├── base.page.ts # Base page object
│ │ ├── login.page.ts # Login page object
│ │ ├── dashboard.page.ts # Dashboard page object
│ │ └── index.ts # Export all pages
│ ├── tests/
│ │ ├── auth.spec.ts # Auth tests
│ │ ├── dashboard.spec.ts # Dashboard tests
│ │ └── checkout.spec.ts # Checkout flow tests
│ ├── utils/
│ │ ├── helpers.ts # Test helpers
│ │ └── test-data.ts # Test data factories
│ └── auth.setup.ts # Global auth setup
├── playwright.config.ts
└── .auth/ # Stored auth state (gitignored)
Use locators that mirror how users interact with the page:
// ✅ BEST: Role-based (accessible, resilient)
page.getByRole('button', { name: 'Submit' })
page.getByRole('textbox', { name: 'Email' })
page.getByRole('link', { name: 'Sign up' })
page.getByRole('heading', { name: 'Welcome' })
// ✅ GOOD: User-facing text
page.getByLabel('Email address')
page.getByPlaceholder('Enter your email')
page.getByText('Welcome back')
page.getByTitle('Profile settings')
// ✅ GOOD: Test IDs (stable, explicit)
page.getByTestId('submit-button')
page.getByTestId('user-avatar')
// ⚠️ AVOID: CSS selectors (brittle)
page.locator('.btn-primary')
page.locator('#submit')
// ❌ NEVER: XPath (extremely brittle)
page.locator('//div[@class="container"]/button[1]')
// Narrow down to specific section
const form = page.getByRole('form', { name: 'Login' });
await form.getByRole('textbox', { name: 'Email' }).fill('[email protected]');
await form.getByRole('button', { name: 'Submit' }).click();
// Filter within a list
const productCard = page.getByTestId('product-card')
.filter({ hasText: 'Pro Plan' });
await productCard.getByRole('button', { name: 'Buy' }).click();
// e2e/pages/base.page.ts
import { PageImplementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
pwa-development
3alinaqi/claude-bootstrap
Productivitysame repoplaywright-cli
7microsoft/playwright-cli
Testingtag: playwrightspring-boot-testing
6github/awesome-copilot
Testingtag: testingaccessibility-testing
6aj-geddes/useful-ai-prompts
Testingtag: testingusability-testing
4refoundai/lenny-skills
Testingtag: testingplaywright-generate-test
4github/awesome-copilot
Testingtag: playwrightReviews
4.6★★★★★52 reviews- IIra Li★★★★★Dec 28, 2024
playwright-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
- MMia Rao★★★★★Dec 20, 2024
Solid pick for teams standardizing on skills: playwright-testing is focused, and the summary matches what you get after install.
- EEvelyn Brown★★★★★Dec 16, 2024
playwright-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- GGanesh Mohane★★★★★Dec 12, 2024
We added playwright-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- CChinedu Martin★★★★★Nov 19, 2024
We added playwright-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- CChinedu Harris★★★★★Nov 11, 2024
playwright-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
- EEvelyn Chen★★★★★Nov 7, 2024
Keeps context tight: playwright-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
- RRahul Santra★★★★★Nov 3, 2024
playwright-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
- VValentina Gill★★★★★Oct 26, 2024
We added playwright-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- PPratham Ware★★★★★Oct 22, 2024
playwright-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 52
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.