test: resolve e2e timeout errors #477
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix E2E Test Timeouts
Problem
Several E2E tests were failing due to 30-second timeouts, preventing reliable CI/CD execution:
pds-checkbox.e2e.tspds-modal.e2e.tspds-progress.e2e.tspds-dropdown-menu.e2e.tspds-tabs.e2e.tsSolution
Implemented comprehensive timeout and stability improvements for E2E testing:
Configuration Updates:
jest.config.jswith 60-second timeout for E2E testssrc/test-setup.jsfor global Jest configurationTest Improvements:
await page.waitForChanges()after component setup to ensure proper hydrationResults
✅ All 645 tests now pass (previously 5 failing)
✅ All 77 test suites complete successfully
✅ Total runtime: 39.3 seconds (improved performance)
✅ Zero timeout failures
Testing