fix: regression where failed events could cause a passing test to display as failed #15037
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.
User facing changelog
Fixes an issue where tests would display as failed if an event (such as an XHR request) failed after the test was already completed. This only affects the display of the test and not what was reported in run mode, so it would not have had an effect on suites running in CI.
Additional details
In addition to the changes described above, there are a number of additional changes that ensure the correct error state is still shown when a user-inputted URL causes a failed
cy.visit()
in studio mode. This was the intent of the original code that caused the regression, and tests have been added for both this intended functionality and to ensure this regression isn't duplicated again in the future. I also added a couple of random extra studio ui tests for good measureHow has the user experience changed?
With the following test code
Before:
After:
PR Tasks