playwright-cursor-rules

Use Playwright fixtures like test, page, and expect for isolation, write descriptive test names, and prefer web-first assertions such as toBeVisible and toHaveText. Extract reusable logic into helper functions and configure global settings in playwright.config.ts.

Prioritize role-based locators like page.getByRole, page.getByLabel, and page.getByText over complex CSS or XPath selectors. Use page.getByTestId when data-testid attributes exist in the application markup.

Define projects in playwright.config.ts using built-in device descriptors from the devices object. Each project targets a browser or device profile, letting one test suite run across Chromium, Firefox, WebKit, and mobile viewports.

Flakiness usually comes from hardcoded timeouts, shared state between tests, or brittle selectors. Replace fixed waits with page.waitFor conditions or web-first assertions, isolate tests with beforeEach hooks, and avoid shared state so tests run reliably in parallel.

Use Playwright's expect with web-first assertions like toBeVisible and toHaveText instead of generic assert statements. Web-first assertions auto-retry until conditions are met, reducing timing-related failures.