smithery.ai

playwright-test

Creates or modifies Playwright E2E tests. Use when testing user flows or verifying UI behavior.

First seen Mar 26, 2026

Installation

$ npx skills add https://smithery.ai

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 smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

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

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,112 B
  • docs SUMMARY.md 118 B

History

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

SKILL.md

Playwright Test Skill

When writing end-to-end tests with Playwright:

File Location

  • Place all E2E tests in the e2e directory.
  • Name files with the .spec.ts suffix (e.g., e2e/login.spec.ts).

Test Structure

import { test, expect } from '@playwright/test';

test.describe('Feature Name', () => {
  test.beforeEach(async ({ page }) => {
    // Setup (e.g., login or navigation)
  });

  test('should perform specific action', async ({ page }) => {
    // Action
    await page.goto('/some-page');
    
    // Assertion
    await expect(page.getByText('Success')).toBeVisible();
  });
});

Best Practices

  • Use locators that are resilient to change (e.g., getByRole, getByText, getByLabel). Avoid CSS selectors relying on implementation details.
  • Group related tests using test.describe.
  • Use await expect(...) for assertions to ensure auto-waiting.
  • Keep tests independent; do not rely on state from previous tests.