tests: Add automatic client-side error checking to e2e tests #812
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.
This change introduces automatic client-side error checking to the end-to-end test harness. Previously, tests would only fail based on their explicit assertions, potentially missing uncaught JavaScript errors that could indicate a broken user experience.
The test harness now monitors for page errors (including console errors and uncaught exceptions) during test execution. If any such errors are detected, the test will fail, providing immediate feedback on runtime issues.
A new option,
checkForPageErrors, has been added to the test runners (testDev,testDeploy,testDevAndDeploy). This allows specific tests to opt-out of this behavior if client-side errors are expected. By default, error checking is enabled.Testing