Automate End-to-End Software Testing

Covers end-to-end testing with Playwright and Cypress across setup, framework-specific patterns, and cross-framework advanced patterns. Playwright: Page Object Model (a LoginPage class wrapping locators and actions like login() behind a reusable API, tested for both successful login and an error-message assertion on failure), fixtures for test data (a typed test.extend that creates a testUser via a database call before the test and tears it down after, yielding isolated per-test data), waiting strategies, and network mocking and interception. Cypress: setup and configuration, custom commands, and cy.intercept for network stubbing. Advanced patterns applicable across both: visual regression testing (toHaveScreenshot assertions on a full page and on a button across its default, hover, and disabled states, with a maxDiffPixels tolerance), parallel testing with sharding (running the same test suite as independent CI jobs via --shard=N/M against isolated test data instead of splitting browser configuration), and accessibility testing (Axe-core's AxeBuilder scanning a full page or a specific form for violations, asserting the violations array is empty). Documents E2E testing fundamentals and test philosophy, best practices, common pitfalls, and a debugging-failing-tests section, plus a worked example with its own inputs and prerequisites and a verification-and-limits section describing what the skill can and cannot confirm.

Use it when writing end-to-end tests for user flows, structuring page objects and fixtures, mocking network requests in tests, adding visual regression or accessibility checks, or parallelizing a test suite with sharding. Skip it for anything unrelated to E2E testing or outside this scope.

Input is a user flow or UI surface to test - a login form, a homepage, a component's visual states; output is the matching Playwright or Cypress test file: a page object, a fixture, a network-mocked test, a screenshot assertion, or an accessibility scan, ready to run in CI.

Playwright (@playwright/test, its fixture system, and toHaveScreenshot) or Cypress (custom commands and cy.intercept) as the test runner, plus @axe-core/playwright for accessibility scanning. Sharding runs through the test runner's own CLI flags in independent CI jobs.

Engineers building or hardening an E2E test suite who need concrete Playwright and Cypress patterns - page objects, fixtures, visual regression, accessibility, and sharding - rather than framework documentation alone. Also covers cross-browser testing, responsive-design validation, establishing E2E testing standards for a team, and setting up the CI/CD pipeline that runs the suite on every change.