fix stale emulator provisioning description in testing docs
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
+2
-2
@@ -41,8 +41,8 @@ The jobs run Maestro CLI 2.6.1 locally on GitHub Actions; Maestro Cloud is not
|
|||||||
used. iOS runs on `macos-26-xlarge` with Xcode 26.4. Android runs on
|
used. iOS runs on `macos-26-xlarge` with Xcode 26.4. Android runs on
|
||||||
`Linux-x64-32core`. Both use Java 17 and the Node and pnpm versions declared in
|
`Linux-x64-32core`. Both use Java 17 and the Node and pnpm versions declared in
|
||||||
`package.json`. The iOS job selects an iPhone 17 simulator running iOS 26.5;
|
`package.json`. The iOS job selects an iPhone 17 simulator running iOS 26.5;
|
||||||
Android uses `reactivecircus/android-emulator-runner` to provision a Pixel 6 AVD
|
Android directly provisions and boots a Pixel 6 AVD with the API 35 Google APIs
|
||||||
with the API 35 Google APIs x86_64 image.
|
x86_64 image using the Android SDK command-line tools.
|
||||||
Both development clients use the `e2e` EAS profile and the same reusable local
|
Both development clients use the `e2e` EAS profile and the same reusable local
|
||||||
EAS build action as the release build workflows; the resulting simulator app
|
EAS build action as the release build workflows; the resulting simulator app
|
||||||
and APK are installed directly on the selected devices.
|
and APK are installed directly on the selected devices.
|
||||||
|
|||||||
Reference in New Issue
Block a user