fix: ensure that Cypress.stop fires all end events appropriately #31780
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.
Additional details
abort
logic until after thetest:after:run:async
event is sent. This will guarantee that the necessary events are received before the run is aborted.Steps to test
Cypress.stop()
How has the user experience changed?
Test Replay is now available for all tests when
Cypress.stop()
is used.PR Tasks
cypress-documentation
?type definitions
?