Our review
Generates end-to-end (e2e) tests using Playwright for web applications by analyzing HTML/JS structure and producing isolated, maintainable tests.
Strengths
- Automatically analyzes HTML/JS to identify key selectors and interactions
- Follows Playwright best practices (data-testid, roles, specific assertions)
- Sets up test environment (playwright.config.ts) and dependencies
- Promotes independent and reproducible tests
Limitations
- Relies on accurate source code analysis; may miss complex dynamic elements
- Does not generate tests for advanced async interactions (WebSockets, complex animations)
- Requires manual verification to ensure generated tests are relevant
Use this skill to quickly create e2e tests for existing or in-development web pages.
Avoid for unit tests or API tests, or when the web app uses highly dynamic frameworks without stable selectors.
Security analysis
SafeThe skill provides instructions for generating Playwright e2e tests. It contains no destructive commands, no exfiltration, no obfuscated payloads. The only shell command is 'python3 -m http.server' for a local dev server, which is a standard practice. No security risks identified.
No concerns found
Examples
Generate Playwright e2e tests for a pomodoro timer application. The app has a start button, pause button, work/break mode toggles, and saves progress to localStorage. Create tests for starting the timer, switching modes, and verifying localStorage persistence.Generate Playwright e2e tests for a modal settings dialog. The page has a button to open a modal, inputs inside the modal, a save button, and a close button. Ensure the modal appears/disappears correctly and settings are saved.name: qc-web description: Generate end-to-end (e2e) tests using Playwright for web applications. Use when creating automated browser tests, testing user flows, UI testing, or writing integration tests for web pages.
QC Web - Playwright E2E Test Generator
Instructions
When generating e2e tests with Playwright, follow these steps:
1. Analyze the Target
- Read the HTML/JavaScript files to understand the page structure
- Identify key user interactions (clicks, inputs, navigation)
- Note important DOM selectors (IDs, classes, data-testid attributes)
- Understand the expected behavior and state changes
2. Test Structure
Create tests in the tests/ directory with .spec.ts extension:
tests/
example.spec.ts
fixtures/
test-data.json
utils/
helpers.ts
3. Writing Tests
Use this template for each test file:
import { test, expect } from '@playwright/test';
test.describe('Feature Name', () => {
test.beforeEach(async ({ page }) => {
await page.goto('/');
});
test('should describe expected behavior', async ({ page }) => {
// Arrange - setup test data/state
// Act - perform user actions
await page.click('button#start');
// Assert - verify expected outcomes
await expect(page.locator('.result')).toBeVisible();
});
});
4. Best Practices
Selectors (in order of preference):
data-testidattributes:page.locator('[data-testid="submit-btn"]')- Role-based:
page.getByRole('button', { name: 'Submit' }) - Text content:
page.getByText('Click me') - CSS selectors:
page.locator('.class-name')
Assertions:
- Use
expectwith specific matchers - Wait for elements:
await expect(locator).toBeVisible() - Check text:
await expect(locator).toHaveText('expected') - Check attributes:
await expect(locator).toHaveAttribute('disabled')
Test Independence:
- Each test should be independent and isolated
- Use
beforeEachfor common setup - Clean up state in
afterEachif needed
5. Configuration
Create playwright.config.ts if not exists:
import { defineConfig } from '@playwright/test';
export default defineConfig({
testDir: './tests',
fullyParallel: true,
retries: process.env.CI ? 2 : 0,
reporter: 'html',
use: {
baseURL: 'http://localhost:8000',
trace: 'on-first-retry',
screenshot: 'only-on-failure',
},
webServer: {
command: 'python3 -m http.server 8000',
url: 'http://localhost:8000',
reuseExistingServer: !process.env.CI,
},
});
6. Running Tests
# Install Playwright
yarn add -D @playwright/test
yarn playwright install
# Run tests
yarn playwright test
# Run with UI mode
yarn playwright test --ui
# Run specific test file
yarn playwright test tests/example.spec.ts
# Debug mode
yarn playwright test --debug
Examples
Timer Application Test
import { test, expect } from '@playwright/test';
test.describe('Pomodoro Timer', () => {
test.beforeEach(async ({ page }) => {
await page.goto('/');
});
test('should start timer when clicking start button', async ({ page }) => {
await page.click('#start-btn');
await expect(page.locator('#timer')).toBeVisible();
await expect(page.locator('#status')).toHaveText('Running');
});
test('should switch between work and break modes', async ({ page }) => {
await page.click('[data-mode="work"]');
await expect(page.locator('.mode-indicator')).toHaveText('Work');
await page.click('[data-mode="shortBreak"]');
await expect(page.locator('.mode-indicator')).toHaveText('Short Break');
});
test('should save progress to localStorage', async ({ page }) => {
await page.click('#start-btn');
await page.waitForTimeout(1000);
await page.click('#pause-btn');
const savedData = await page.evaluate(() => {
return localStorage.getItem('pomodoroTimeline');
});
expect(savedData).not.toBeNull();
});
});
Modal/Settings Test
test.describe('Settings Modal', () => {
test('should open and close settings modal', async ({ page }) => {
await page.click('#settings-btn');
await expect(page.locator('.modal')).toBeVisible();
await page.click('.modal-close');
await expect(page.locator('.modal')).toBeHidden();
});
test('should switch between tabs', async ({ page }) => {
await page.click('#settings-btn');
await page.click('[data-tab="sound"]');
await expect(page.locator('.tab-content[data-tab="sound"]')).toBeVisible();
await page.click('[data-tab="library"]');
await expect(page.locator('.tab-content[data-tab="library"]')).toBeVisible();
});
});
Form Interaction Test
test('should handle form submission', async ({ page }) => {
await page.fill('input[name="duration"]', '30');
await page.selectOption('select#mode', 'work');
await page.check('input#notifications');
await page.click('button[type="submit"]');
await expect(page.locator('.success-message')).toBeVisible();
});
Version History
- v1.0.0 (2025-12-03): Initial release
TDD Red-Green-Refactor
Testing
Skill that guides Claude through the complete TDD cycle.
Web Accessibility Audit
Testing
Performs a comprehensive web accessibility audit following WCAG standards.
UAT Test Case Generator
Testing
Generates structured and comprehensive user acceptance test cases.