Repository navigation
Run Cypress 16 tests in Chrome - #4634
Merged
Merged
Conversation
|
…me-for-cypress # Conflicts: # .github/workflows/pr.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cypress 16 deprecates its bundled Electron browser, but our E2E scripts still default to Electron and CI carries an Electron-only GPU workaround.
This runs source, built, interactive, and accessibility Cypress commands in Chrome, removes the GPU workaround, and updates
cypress-real-eventsto 1.15.1 (the release whose peer range includes Cypress 16).The latest
cypress-axepackage still only declares support through Cypress 15. Upstream merged Cypress 16 support, but its release pipeline is currently blocking publication, so this leaves 1.7.0 in place instead of pinning Cypress backward or depending on an unreleased commit.