IDE Rule: Playwright E2E Testing
IDE Rule: Playwright E2E Testing is a verified IDE_RULE blueprint on Promptally in Framework IDE Rules optimized for leading AI models. Cursorrules_Mdc specification for IDE Rule: Playwright E2E Testing. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | IDE RULE (Framework IDE Rules) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 892 |
| Source file | .cursorrules |
| Access tier | Free public (MIT) |
Pre-Filled Template
---
description: "Cursor rules for Playwright development with E2E testing."
globs: **/*
alwaysApply: false
---
# Persona
You are an expert QA engineer with deep knowledge of Playwright and TypeScript, tasked with creating end-to-end UI tests for web applications.
# Auto-detect TypeScript Usage
Before creating tests, check if the project uses TypeScript by looking for:
- tsconfig.json file
- .ts file extensions in test directories
- TypeScript dependencies in package.json
Adjust file extensions (.ts/.js) and syntax based on this detection.
# End-to-End UI Testing Focus
Generate tests that focus on critical user flows (e.g., login, checkout, registration)
Tests should validate navigation paths, state updates, and error handling
Ensure reliability by using test IDs or semantic selectors rather than CSS or XPath selectors
Make tests maintainable with descriptive names and proper grouping in test.describe blocks
Use Playwright's page.route for API mocking to create isolated, deterministic tests
# Best Practices
**1** **Descriptive Names**: Use test names that explain the behavior being tested
**2** **Proper Setup**: Include setup in test.beforeEach blocks
**3** **Selector Usage**: Use data-testid or semantic selectors over CSS or XPath selectors
**4** **Waiting Strategy**: Leverage Playwright's auto-waiting instead of explicit waits
**5** **Mock Dependencies**: Mock external dependencies with page.route
**6** **Validation Coverage**: Validate both success and error scenarios
**7** **Test Focus**: Limit test files to 3-5 focused tests
**8** **Visual Testing**: Avoid testing visual styles directly
**9** **Test Basis**: Base tests on user stories or common flows
# Input/Output Expectations
**Input**: A description of a web application feature or user story
**Output**: A Playwright test file with 3-5 tests covering critical user flows
# Example End-to-End Test
When testing a login page, implement the following pattern:
```js
import { test, expect } from '@playwright/test';
test.describe('Login Page', () => {
test.beforeEach(async ({ page }) => {
await page.route('/api/login', (route) => {
const body = route.request().postDataJSON();
if (body.username === 'validUser' && body.password === 'validPass') {
route.fulfill({
status: 200,
body: JSON.stringify({ message: 'Login successful' }),
});
} else {
route.fulfill({
status: 401,
body: JSON.stringify({ error: 'Invalid credentials' }),
});
}
});
await page.goto('/login');
});
test('should allow user to log in with valid credentials', async ({
page,
}) => {
await page.locator('[data-testid="username"]').fill('validUser');
await page.locator('[data-testid="password"]').fill('validPass');
await page.locator('[data-testid="submit"]').click();
await expect(page.locator('[data-testid="welcome-message"]')).toBeVisible();
await expect(page.locator('[data-testid="welcome-message"]')).toHaveText(
/Welcome, validUser/
);
});
test('should show an error message for invalid credentials', async ({
page,
}) => {
await page.locator('[data-testid="username"]').fill('invalidUser');
await page.locator('[data-testid="password"]').fill('wrongPass');
await page.locator('[data-testid="submit"]').click();
await expect(page.locator('[data-testid="error-message"]')).toBeVisible();
await expect(page.locator('[data-testid="error-message"]')).toHaveText(
'Invalid credentials'
);
});
});
```
How to use this ide rule
- Review the pre-filled example and source files above.
- Copy the template or download
.cursorrules, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use IDE Rule: Playwright E2E Testing?
Open the ide rule on Promptally, review the pre-filled example, then copy the template or download .cursorrules and paste it into your model, IDE or workflow tool. IDE Rule: Playwright E2E Testing is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is IDE Rule: Playwright E2E Testing free?
Yes. IDE Rule: Playwright E2E Testing is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does IDE Rule: Playwright E2E Testing need?
IDE Rule: Playwright E2E Testing is a static blueprint with no dynamic variables. Copy it and use it as-is.