e2e-testing-automation

End-to-end (E2E) testing validates complete user workflows from the UI through all backend systems, ensuring the entire application stack works together correctly from a user's perspective. E2E tests simulate real user interactions with browsers, handling authentication, navigation, form submissions, and validating results. Minimal working example: Detailed implementations in the references/ directory: - Overview - When to Use - Quick Start - Reference Guides - Best Practices - Testing critical user journeys (signup, checkout, login) - Validating multi-step workflows - Testing across different browsers and devices - Regression testing for UI changes - Verifying frontend-backend integration - Testing with real user interactions (clicks, typing, scrolling) - Smoke testing deployments - Use data-testid attributes for stable selectors - Implement Page Object Model for maintainability - Test critical user journeys thoroughly - Run tests in multiple browsers (cross-browser testing) - Use explicit waits instead of sleep/timeouts - Clean up test data after each test - Take screenshots on failures - Parallelize test execution where possible - Use brittle CSS selectors (like nth-child) - Test every possible UI combination (focus on critical paths) - Share state between tests - Use fixed delays (sleep/timeout) - Ignore flaky tests - Run E2E tests for unit-level testing - Test third-party...