playwright-expert

Create a class per page that exposes locators as readonly properties and actions as methods, then instantiate it in tests with the page fixture. Combine with custom fixtures via test.extend to share authenticated pages and page objects across tests.

Enable trace: 'on-first-retry' in playwright.config.ts, rerun with retries, and inspect the trace viewer timeline. Replace waitForTimeout calls with locator waits like waitFor({ state: 'visible' }) or waitForResponse, then verify stability with --repeat-each=10.

Prefer getByRole with an accessible name, then getByLabel or getByPlaceholder for forms, and getByTestId for non-semantic elements. Avoid CSS class selectors and XPath because they break when styling or markup changes.

Use page.route with a URL pattern and call route.fulfill to return a mock status and JSON body, or route.fetch to modify real responses. You can also record and replay responses with routeFromHAR for deterministic tests.

Yes. Install browsers with npx playwright install --with-deps, run npx playwright test, and upload the playwright-report directory as an artifact. Set retries and a single worker via environment checks on process.env.CI.

waitForTimeout pauses for a fixed duration regardless of actual page state, causing slow or flaky tests. Playwright locators auto-wait for actionability, and explicit waits like toBeVisible or waitForResponse synchronize on real conditions.