playwright

Stable Playwright E2E tests are achieved by prioritizing resilient locators like getByRole, getByLabel, and getByText, and by snapshotting real DOM state through MCP exploration before authoring to avoid brittle selectors.

Playwright page objects should use a BasePage pattern to centralize common behavior and helpers, keeping spec files structured with a single-spec-per-feature approach under dedicated folders to ensure reproducible test documentation.

Playwright test failures often stem from fragile locators; you should inspect real DOM state via MCP exploratory snapshots first, and apply selector priority rules using getByRole or getByLabel over brittle CSS or XPath locators.

You need the Page Object Model for Playwright E2E scenarios when centralizing common behavior and reducing duplicated actions across feature pages, moving shared logic to BasePage or utilities for better refactoring and reuse.

Document Playwright E2E test cases using a lightweight markdown format alongside spec and page object files, placing them under dedicated tests/{page-name} folders with standardized tagging conventions for reproducible documentation.

Yes, these Playwright E2E patterns support TypeScript testing environments, applying typed Page Object Models, BasePage conventions, and MCP exploratory workflows to generate stable UI tests for web applications.