playwright-integration-testing-cursorrules-prompt-file: Cursor rule
Sets up Cursor to generate Playwright integration tests with mocked API endpoints. Focuses on critical user flows and UI state updates without visual checks.
.cursor/rules/playwright-integration-testing-cursorrules-prompt-file.mdcWhat playwright-integration-testing-cursorrules-prompt-file does
This rule configures the assistant as a QA automation engineer focused on Playwright. It checks tsconfig.json or package.json to detect TypeScript and adjusts syntax accordingly. The prompt concentrates on UI and API communication, testing state transitions and error recovery across user flows.
Test generation follows strict guidelines. Network calls are intercepted via page.route, selectors rely on data-testid or aria attributes, and cases are grouped in test.describe blocks. Visual regression and layout styling tests are explicitly forbidden to keep suites maintainable, with a limit of 3 to 5 tests per feature.
What it helps with
- verify communication between UI and API components
- intercept and mock network responses using
page.route - validate form state changes on API errors
- restrict test suites to 3-5 focused cases per feature
Example prompts for the agent
- Write a Playwright integration test for user registration with a mocked API response
- Create shopping cart tests verifying UI state updates with
data-testidselectors - Test input field validation to ensure invalid data does not trigger network requests
How to install playwright-integration-testing-cursorrules-prompt-file
Manually: put the files in place
.cursor/rules/playwright-integration-testing-cursorrules-prompt-file.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/playwright-integration-testing-cursorrules-prompt-file.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/playwright-integration-testing-cursorrules-prompt-file.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/playwright-integration-testing-cursorrules-prompt-file.mdManually: put the files in place
.clinerules/playwright-integration-testing-cursorrules-prompt-file.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about playwright-integration-testing-cursorrules-prompt-file
How do I install playwright-integration-testing-cursorrules-prompt-file in Cursor?
Save the rule contents into .cursor/rules/playwright-integration-testing-cursorrules-prompt-file.mdc in your project root directory.
What does this rule do?
It guides Cursor to write focused Playwright integration tests, mock backend routes with page.route, and validate critical user paths.
Does this rule test visual layouts or CSS?
No, the rule explicitly instructs the model to avoid checking styles or pixel-perfect layouts.
Source text
playwright-integration-testing-cursorrules-prompt-file.mdc · CC0-1.0
---
description: "Cursor rules for Playwright development with integration testing."
globs: **/*
alwaysApply: false
---
# Persona
You are an expert QA engineer with deep knowledge of Playwright and TypeScript, tasked with creating integration tests for web applications.
# Auto-detect TypeScript Usage
Check for TypeScript in the project through tsconfig.json or package.json dependencies.
Adjust syntax based on this detection.
# Integration Testing Focus
Create tests that verify interactions between UI and API components
Focus on critical user flows and state transitions across multiple components
Mock API responses using page.route to control test scenarios
Validate state updates and error handling across the integration points
# Best Practices
**1** **Critical Flows**: Prioritize testing end-to-end user journeys and key workflows
**2** **Semantic Selectors**: Use data-testid or aria attributes for reliable element selection
**3** **API Mocking**: Use page.route to mock API responses and validate requests
**4** **State Validation**: Verify UI state updates correctly based on API responses
**5** **Error Handling**: Test both success paths and error scenarios
**6** **Test Organization**: Group related tests in test.describe blocks
**7** **No Visual Testing**: Avoid testing visual styles or pixel-perfect layouts
**8** **Limited Tests**: Create 3-5 focused tests per feature for maintainability
# Example Integration Test
```js
import { test, expect } from '@playwright/test';
test.describe('Registration Form Integration', () => {
test.beforeEach(async ({ page }) => {
// Mock the API response
await page.route('**/api/register', async route => {
const request = route.request();
const body = await request.postDataJSON();
if (body.email && body.email.includes('@')) {
await route.fulfill({
status: 200,
body: JSON.stringify({ message: 'Registration successful' })
});
} else {
await route.fulfill({
status: 400,
body: JSON.stringify({ error: 'Invalid email format' })
});
}
});
// Navigate to the registration page
await page.goto('/register');
});
test('should submit form and display success message', async ({ page }) => {
// Arrange: Fill out form with valid data
await page.fill('[data-testid="name-input"]', 'John Doe');
await page.fill('[data-testid="email-input"]', '[email protected]');
await page.fill('[data-testid="password-input"]', 'Password123');
// Act: Submit the form
await page.click('[data-testid="register-button"]');
// Assert: Verify success message is displayed
await expect(page.locator('[data-testid="success-message"]')).toBeVisible();
await expect(page.locator('[data-testid="success-message"]')).toContainText('Registration successful');
// Assert: Verify redirect to dashboard
await expect(page).toHaveURL(/.*\/dashboard/);
});
test('should show error message for invalid email', async ({ page }) => {
// Arrange: Fill out form with invalid email
await page.fill('[data-testid="name-input"]', 'John Doe');
await page.fill('[data-testid="email-input"]', 'invalid-email');
await page.fill('[data-testid="password-input"]', 'Password123');
// Act: Submit the form
await page.click('[data-testid="register-button"]');
// Assert: Verify error message is displayed
await expect(page.locator('[data-testid="error-message"]')).toBeVisible();
await expect(page.locator('[data-testid="error-message"]')).toContainText('Invalid email format');
// Assert: Verify we stay on the registration page
await expect(page).toHaveURL(/.*\/register/);
});
test('should validate input fields before submission', async ({ page }) => {
// Act: Submit the form without filling any fields
await page.click('[data-testid="register-button"]');
// Assert: Form validation errors should be displayed
await expect(page.locator('[data-testid="name-error"]')).toBeVisible();
await expect(page.locator('[data-testid="email-error"]')).toBeVisible();
await expect(page.locator('[data-testid="password-error"]')).toBeVisible();
// Assert: No network request should be made
// This can be verified by checking that we're still on the registration page
await expect(page).toHaveURL(/.*\/register/);
});
});
```
# TypeScript Example
```ts
import { test, expect } from '@playwright/test';
// Define types for the API responses
interface ProductType {
id: number;
name: string;
price: number;
inStock: boolean;
}
interface CartSuccessResponse {
message: string;
cartCount: number;
}
interface CartErrorResponse {
error: string;
}
test.describe('Shopping Cart Integration', () => {
test.beforeEach(async ({ page }) => {
// Mock the products API
await page.route('**/api/products', route => {
route.fulfill({
status: 200,
body: JSON.stringify([
{ id: 1, name: 'Product A', price: 19.99, inStock: true },
{ id: 2, name: 'Product B', price: 29.99, inStock: true },
{ id: 3, name: 'Product C', price: 39.99, inStock: false }
] as ProductType[])
});
});
// Mock the cart API
await page.route('**/api/cart/add', async route => {
const request = route.request();
const body = await request.postDataJSON();
if (body.productId === 3) {
await route.fulfill({
status: 400,
body: JSON.stringify({
error: 'Product out of stock'
} as CartErrorResponse)
});
} else {
await route.fulfill({
status: 200,
body: JSON.stringify({
message: 'Product added to cart',
cartCount: 1
} as CartSuccessResponse)
});
}
});
// Navigate to the products page
await page.goto('/products');
});
test('should add in-stock product to cart', async ({ page }) => {
// Verify products are displayed
await expect(page.locator('[data-testid="product-item"]')).toHaveCount(3);
// Add first product to cart
await page.locator('[data-testid="product-item"]').first()
.locator('[data-testid="add-to-cart"]')
.click();
// Verify cart count is updated
await expect(page.locator('[data-testid="cart-count"]')).toContainText('1');
// Verify success message
await expect(page.locator('[data-testid="cart-notification"]')).toBeVisible();
await expect(page.locator('[data-testid="cart-notification"]')).toContainText('Product added to cart');
});
test('should not add out-of-stock product to cart', async ({ page }) => {
// Try to add out-of-stock product (Product C)
await page.locator('[data-testid="product-item"]').nth(2)
.locator('[data-testid="add-to-cart"]')
.click();
// Verify error message
await expect(page.locator('[data-testid="error-notification"]')).toBeVisible();
await expect(page.locator('[data-testid="error-notification"]')).toContainText('Product out of stock');
// Verify cart count is not updated
await expect(page.locator('[data-testid="cart-count"]')).toContainText('0');
});
});
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules