e2e-testing

Reduce flaky tests in Playwright by applying retry strategies, conditional skips, and quarantine patterns. This skill provides configurations to diagnose race conditions and timing issues, stabilizing automated end-to-end runs under CI/CD.

The best way to organize Playwright test code is using the Page Object Model. This skill encourages page classes and locators to create readable, reusable test code, reducing unmaintainable test suites.

Configure Playwright for cross-browser parallel runs using example configurations for device projects, retries, and environment-aware CI settings. This skill provides setups to orchestrate automated test suites across different environments.

Capture Playwright artifacts like screenshots, traces, and videos using built-in artifact collection patterns. This skill provides capture configurations and GitHub Actions workflows for running and uploading reports.

Yes, you can test web3 wallet interactions and financial flows with Playwright. This skill provides specialized guidance for wallet mocking and safe testing of critical financial scenarios under CI/CD.

Playwright authentication and search E2E tests fail in CI often due to race conditions or environment settings. This skill provides scaffolds for these flows and patterns to mitigate timing issues and standardize orchestration.