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.
1.6 KiB
1.6 KiB
Sprint 1: E2E Test Improvements
Last Updated: February 2, 2026
What We Fixed
During Sprint 1, we resolved critical issues affecting E2E test reliability and performance.
Problem: Tests Were Timing Out
What was happening: Some tests would hang indefinitely or timeout after 30 seconds, especially in CI/CD pipelines.
Root cause:
- Config reload overlay was blocking test interactions
- Feature flag propagation was too slow during high load
- API polling happened unnecessarily for every test
What we did:
- Added smart detection to wait for config reloads to complete
- Increased timeouts to accommodate slower environments
- Implemented request caching to reduce redundant API calls
Result: Test pass rate increased from 96% to 100% ✅
Performance Improvements
- Before: System settings tests took 23 minutes
- After: Same tests now complete in 16 minutes
- Improvement: 31% faster execution
What You'll Notice
- Tests are more reliable and less likely to fail randomly
- CI/CD pipelines complete faster
- Fewer "Test timeout" errors in GitHub Actions logs
For Developers
If you're writing new E2E tests, the helpers in tests/utils/wait-helpers.ts and tests/utils/ui-helpers.ts now automatically handle:
- Config reload overlays
- Feature flag propagation
- Switch component interactions
Follow the examples in tests/settings/system-settings.spec.ts for best practices.