e2e-testing

Reduce Playwright E2E test flakiness in CI by configuring parallelism, retries, environment-aware timeouts, and quarantine patterns. Capture actionable artifacts like screenshots, traces, and videos to diagnose race conditions and network timing issues across local and pipeline runs.

Organize Playwright test suites using Page Object Model patterns to separate UI element locators from test logic. This structured approach provides clear examples for maintainable test code, ensuring reliable authentication flows and multi-project testing configuration.

Capture Playwright artifacts in GitHub Actions by configuring reporters to generate screenshots, traces, and videos during E2E test runs. Use a sample CI workflow to install Playwright, execute tests with environment-aware timeouts, and upload these artifacts for post-run diagnosis.

Mock wallet and Web3 interactions in Playwright E2E testing using specialized mocking patterns. Apply guarded flows for financial or critical transactions with environment-aware skips to ensure test stability without compromising sensitive transaction validation.

Playwright configuration dictates parallel execution, retries, reporters, and timeouts for multi-project testing. Proper configuration ensures consistent E2E suite behavior across local and CI environments, preventing race conditions and capturing actionable artifacts for flaky test investigation.

Diagnose flaky Playwright tests using repeat-and-diagnose commands and quarantine patterns to isolate race conditions. Apply retry strategies and analyze captured traces and videos to identify network timing issues and stabilize critical E2E flows.