Performance testing implemented
CI Pipeline / test (18) (pull_request) Failing after 49s
CI Pipeline / test (20) (pull_request) Failing after 53s
CI Pipeline / e2e (chromium) (pull_request) Failing after 21m9s
CI Pipeline / e2e (firefox) (pull_request) Failing after 25m13s
CI Pipeline / visual-regression (pull_request) Failing after 7m9s
CI Pipeline / performance (pull_request) Failing after 2m1s
CI Pipeline / storybook (pull_request) Failing after 1m32s
CI Pipeline / lint (pull_request) Failing after 44s
CI Pipeline / build (pull_request) Failing after 1m43s
CI Pipeline / e2e (webkit) (pull_request) Failing after 23m14s

This commit is contained in:
adilallo
2025-08-29 13:53:00 -06:00
parent f7621d2086
commit d300772f19
8 changed files with 1823 additions and 10 deletions
+5 -4
View File
@@ -6,10 +6,11 @@ This document outlines our comprehensive testing strategy that properly separate
## Current Test Status
- **184 total tests** across the project
- **176 tests passing** (95.7% success rate)
- **8 tests failing** (all related to multiple element instances)
- **13 test files** covering all major components
- **236 total tests** across the project
- **227 tests passing** (96.2% success rate)
- **9 tests failing** (performance and interaction tests)
- **15 test files** covering all major components
- **Performance Monitoring**: Comprehensive regression detection and budget enforcement
## Testing Philosophy