ca477c48d4
- Added clarity and structure to README files, including recent updates and getting started sections. - Improved manual verification documentation for CrowdSec authentication, emphasizing expected outputs and success criteria. - Updated debugging guide with detailed output examples and automatic trace capture information. - Refined best practices for E2E tests, focusing on efficient polling, locator strategies, and state management. - Documented triage report for DNS Provider feature tests, highlighting issues fixed and test results before and after improvements. - Revised E2E test writing guide to include when to use specific helper functions and patterns for better test reliability. - Enhanced troubleshooting documentation with clear resolutions for common issues, including timeout and token configuration problems. - Updated tests README to provide quick links and best practices for writing robust tests.
436 B
436 B
E2E Testing & Debugging Guide
Recent Updates: See Sprint 1 Improvements for information about recent E2E test reliability and performance enhancements (February 2026).
Getting Started with E2E Tests
- Running Tests:
npm run e2e - All Browsers:
npm run e2e:all - Headed UI on headless Linux:
npm run e2e:ui:headless-server— seedocs/development/running-e2e.mdfor details