[Mobile] - Fix React Native iOS E2E tests #49823
Merged
Conversation
This file contains 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
geriux
added
[Status] In Progress
|
Flaky tests detected in 3c239f7. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4698721445
|
|
Size Change: 0 B Total Size: 1.37 MB ℹ️ View Unchanged
|
geriux
force-pushed
the
rnmobile/fix-ios-e2e-issue
branch
from
cda427a
to
7a939c2
Compare
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.
What?
This PR fixes the current failures with the React Native E2E iOS tests.
Why?
They're currently failing in
trunk. I haven't found out why this started happening but it could be something that changed in CI most probably.How?
It updates the macOS runner to
macos-12, and Xcode to13.3.1.It also now forces launching the simulator before starting to run the tests, this might be the issue we were having, since booting up the simulator takes up close to 5 minutes.
Testing Instructions
CI checks should pass, maybe re-trigger the iOS tests.
Testing Instructions for Keyboard
N/A
Screenshots or screencast
N/A