@radhya/mach 2.0.5 → 2.0.7
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 +4 -0
- package/dist/index.js +245 -132
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -59,6 +59,8 @@ mach maestro --build-id <buildId>
|
|
|
59
59
|
mach maestro --local --build-id <buildId>
|
|
60
60
|
mach maestro --build-id <buildId> --maestro-use-build-source
|
|
61
61
|
mach maestro --build-id <buildId> --wait
|
|
62
|
+
mach maestro --latest --platform ios --maestro-env MAESTRO_TEST_EMAIL --maestro-env MAESTRO_TEST_PASSWORD
|
|
63
|
+
mach maestro --platform ios --local --maestro-flows .maestro-authenticated --maestro-env MAESTRO_TEST_EMAIL --maestro-env MAESTRO_TEST_PASSWORD
|
|
62
64
|
```
|
|
63
65
|
|
|
64
66
|
Mach manages the test execution infrastructure for you, so projects do not need a separate Maestro Cloud setup.
|
|
@@ -66,6 +68,7 @@ Managed Android Maestro runs need an APK artifact and a `.maestro` flow file or
|
|
|
66
68
|
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
69
|
Managed Maestro is billed from the Pay as you go wallet after the runner completes. Default pricing is $0.50 for the first 15 minutes, then $0.10 per additional 10-minute block; admins can change these rates from Dashboard Admin > Pricing.
|
|
68
70
|
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.
|
|
71
|
+
Use `--maestro-env <name>` for local or managed runs that need test credentials or other dynamic values. The flag is repeatable and also accepts comma-separated names. Local runs forward only names that exist in the shell or loaded dotenv environment, and the startup log lists every forwarded name. Managed runs store requested values encrypted, pass them to the iOS or Android Maestro command, redact values from runner logs, and fall back to the Mach server environment when a value is not present in the CLI environment.
|
|
69
72
|
|
|
70
73
|
Useful options:
|
|
71
74
|
|
|
@@ -77,6 +80,7 @@ Useful options:
|
|
|
77
80
|
| `--maestro-retries <n>` | Retry count for failed runs, from 0 to 10 |
|
|
78
81
|
| `--maestro-record` | Enable recording when supported by the runner |
|
|
79
82
|
| `--maestro-use-build-source` | Use flows from the build source snapshot instead of local upload |
|
|
83
|
+
| `--maestro-env <name>` | Forward one env var to Maestro; repeat or comma-separate names |
|
|
80
84
|
| `--local` | Run `maestro test` locally instead of queueing a cloud runner |
|
|
81
85
|
| `--wait` | Wait for managed tests and exit non-zero if the run fails |
|
|
82
86
|
| `--wait-timeout <minutes>` | Maximum time to wait for a managed run, defaults to 60 |
|