@radhya/mach 1.9.8 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -16
- package/dist/index.js +124 -113
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -56,20 +56,30 @@ Mach's E2E testing layer is being implemented to run Maestro without requiring M
|
|
|
56
56
|
mach build android --profile e2e-test --maestro
|
|
57
57
|
mach maestro --latest --platform android --profile e2e-test
|
|
58
58
|
mach maestro --build-id <buildId>
|
|
59
|
+
mach maestro --local --build-id <buildId>
|
|
60
|
+
mach maestro --build-id <buildId> --maestro-use-build-source
|
|
61
|
+
mach maestro --build-id <buildId> --wait
|
|
59
62
|
```
|
|
60
63
|
|
|
61
64
|
Mach manages the test execution infrastructure for you, so projects do not need a separate Maestro Cloud setup.
|
|
62
|
-
Managed Android Maestro runs need an APK artifact and a `.maestro` flow file or directory
|
|
65
|
+
Managed Android Maestro runs need an APK artifact and a `.maestro` flow file or directory. By default, `mach maestro --maestro-flows .maestro` uploads the local flow folder for that run when the path exists in the current project. If the local path is not present, Mach falls back to the build source snapshot.
|
|
66
|
+
Managed Android runners use emulators, so the tested APK must include `x86_64`. Mach automatically includes emulator ABI support when you build with `--maestro`, when the profile name looks like `maestro`/`e2e`/`test`, or when the build profile sets `"android": { "emulator": true }`.
|
|
67
|
+
Use `mach maestro --local` to run the same flows on your connected local emulator/device. With `--build-id`, Mach downloads and installs the build artifact first; without a build or artifact flag, it runs against the app already installed locally.
|
|
63
68
|
|
|
64
69
|
Useful options:
|
|
65
70
|
|
|
66
|
-
| Flag
|
|
67
|
-
|
|
|
68
|
-
| `--maestro`
|
|
69
|
-
| `--maestro-flows <path>`
|
|
70
|
-
| `--maestro-device <name>`
|
|
71
|
-
| `--maestro-retries <n>`
|
|
72
|
-
| `--maestro-record`
|
|
71
|
+
| Flag | Description |
|
|
72
|
+
| --------------------------- | ------------------------------------------------------------- |
|
|
73
|
+
| `--maestro` | Queue tests automatically after a successful `mach build` |
|
|
74
|
+
| `--maestro-flows <path>` | Flow file or directory, defaults to `.maestro` |
|
|
75
|
+
| `--maestro-device <name>` | Managed runner device profile, defaults to Android Pixel 6 |
|
|
76
|
+
| `--maestro-retries <n>` | Retry count for failed runs, from 0 to 10 |
|
|
77
|
+
| `--maestro-record` | Enable recording when supported by the runner |
|
|
78
|
+
| `--maestro-use-build-source` | Use flows from the build source snapshot instead of local upload |
|
|
79
|
+
| `--local` | Run `maestro test` locally instead of queueing a cloud runner |
|
|
80
|
+
| `--wait` | Wait for managed tests and exit non-zero if the run fails |
|
|
81
|
+
| `--wait-timeout <minutes>` | Maximum time to wait for a managed run, defaults to 60 |
|
|
82
|
+
| `--wait-interval <seconds>` | Polling interval for `--wait`, defaults to 15 |
|
|
73
83
|
|
|
74
84
|
## Cloud Builds
|
|
75
85
|
|
|
@@ -296,18 +306,20 @@ Create a `mach.config.json` in your project root:
|
|
|
296
306
|
| `ios.ascAppId` | App Store Connect app id. Optional when Mach can find the app by bundle ID; recommended for reliable iOS buildNumber lookup |
|
|
297
307
|
| `ios.buildNumber` | Set to `"auto"` to let Mach resolve the next iOS CFBundleVersion from App Store Connect and seed the server-side build counter |
|
|
298
308
|
| `android.package` | Android package name used for signing, Google Play lookup, and submit |
|
|
299
|
-
| `android.versionCode` | Set to `"auto"` to let store builds resolve the next versionCode via Google Play
|
|
309
|
+
| `android.versionCode` | Set to `"auto"` to let store builds resolve the next versionCode via Google Play |
|
|
300
310
|
|
|
301
311
|
### Profile Properties
|
|
302
312
|
|
|
303
|
-
| Property | Description
|
|
304
|
-
| ------------------------ |
|
|
305
|
-
| `extends` | Inherit settings from another profile
|
|
306
|
-
| `environment` | Dashboard Secret Environment to use (`development`, `staging`, `production`)
|
|
307
|
-
| `developmentClient` | `true` to build with `expo-dev-client`
|
|
313
|
+
| Property | Description |
|
|
314
|
+
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
315
|
+
| `extends` | Inherit settings from another profile |
|
|
316
|
+
| `environment` | Dashboard Secret Environment to use (`development`, `staging`, `production`) |
|
|
317
|
+
| `developmentClient` | `true` to build with `expo-dev-client` |
|
|
308
318
|
| `distribution` | `development` for iOS development signing, `internal` for ad-hoc/internal testing builds, or `store` for App Store / Play Store release builds |
|
|
309
|
-
| `
|
|
310
|
-
| `
|
|
319
|
+
| `android.emulator` | `true` to include Android emulator ABI support (`x86_64`) for Maestro/e2e APK builds |
|
|
320
|
+
| `android.architectures` | Override Android release ABIs, for example `armeabi-v7a,arm64-v8a,x86_64` |
|
|
321
|
+
| `preBuild` / `postBuild` | Shell command or script reference to run around the build |
|
|
322
|
+
| `envGroups` | Array of environment group names to merge into this profile |
|
|
311
323
|
|
|
312
324
|
### Environment Groups
|
|
313
325
|
|