-
Notifications
You must be signed in to change notification settings - Fork 4.6k
test: E2E test setup script creates Android emulator #55898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Simplify E2E test environment setup by creating the required Android emualtors if they are not present.
The setup script now manages these previously documented steps.
Reduce verbosity and improve consistency of log messages.
The `avdmanager` command is unavailable, also the CI server generally provides its own emulator.
This CLI is required for creating emulators.
|
👋🏻 @geriux. I believe we once discussed the following error when running I was able to resolve this error on my local machine by adding the following to my path before my existing diff --git a/zshrc b/zshrc
index be83a92..d1ebb77 100644
--- a/zshrc.local
+++ b/zshrc.local
@@ -36,6 +36,7 @@ export TERM="xterm-256color-italic"
# Set Android SDK for React Native development
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/emulator
+export PATH=$PATH:$ANDROID_HOME/cmdline-tools/latest/bin
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools |
|
Flaky tests detected in 6fae855. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6773444501
|
These values need to update if the `device-config.json` updates.
|
Sorry for the late commits. This should actually be ready for review now. 😅 |
Thank you! Now I'm able to run |
geriux
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nice work with the script updates! ⭐
- ✅ Created the simulator correctly when it didn't exist.
- ✅ Skipped creating the simulator correctly when it existed.
- ✅ Android tests ran as expected after creating the simulator using the script.
What?
Expand the E2E test setup script to ensure the required iOS simulators are
available.
Why?
Relates to #55251. Simplify setting
up the E2E test environment by automating the process for creating the required
Android emulators.
How?
Update the E2E test setup script to leverage
avdmanagerto create the requiredAndroid emulators. Remove now unneeded documentation of manual steps.
Testing Instructions
With required emulator unavailable
avdmanager delete avd -n <device-id>.npm run native test:e2e:setupWith required emulator available
emulator -list-avds.npm run native test:e2e:setupTesting Instructions for Keyboard
n/a
Screenshots or screencast
n/a