Repository navigation
Added
-
testingbot rerun --id <projectId>: re-runs flows of an earlier Maestro project on the same devices, without uploading anything again. By default every failed flow is re-run.--run <runIds>limits it to some runs (devices), and--flow <names>picks flows by name or ID, even ones that passed. Each flow runs again as a new attempt inside its original run, so the dashboard and reports show the latest result. The live table, exit code,--reportand--download-artifactscover only the re-run runs.--asyncqueues the re-run and exits. Ctrl-C detaches without cancelling. -
Proxy support:
--proxy <url>on every command, orHTTPS_PROXY/HTTP_PROXY/ALL_PROXYwithNO_PROXY. API calls, uploads, the live-updates WebSocket, the tunnel download and the tunnel itself go through it (HTTPS via CONNECT). Before, behind a proxy the pre-flight connectivity check failed with "No internet connection", and axios sent HTTPS requests to the proxy without CONNECT. -
Job summary and annotations in CI: in GitHub Actions a results table is appended to
$GITHUB_STEP_SUMMARYand every failed flow or run gets an::errorannotation; in Azure Pipelines the table is attached to the build and failures are logged as errors. Formaestro,espresso,xcuitestandstatus.TESTINGBOT_CI_SUMMARY=0turns it off. -
testingbot maestro --cancel-previous: before starting, cancels your queued or running runs of the same repository and branch or pull request from an earlier commit (cancelPreviouson the run API). Runs on the same commit are left alone. -
testingbot maestrodetects the repository URL, branch, commit and pull request in GitHub Actions, GitLab CI, Bitbucket Pipelines, Azure Pipelines and CircleCI and sends them as run metadata (repoUrlis new), so the dashboard can link to the commit and PR on any Git host. On a GitHub pull request the PR's head commit is used, not the merge commit. Explicit flags win. -
testingbot espressoandtestingbot xcuitesttake the same CI/CD metadata asmaestro:--branch,--pr-url,-m/--metadataand the CI environment detection, through one shared code path. -
--retry <count>,--download-artifacts [all|failed]and--artifacts-output-dirfortestingbot espressoandtestingbot xcuitest. A retried run is started again on the uploaded app; the last attempt decides the exit code, the--reportand the artifacts. Artifacts (video, logs, screenshots) are zipped with a folder per run, likemaestro. -
--timeout <minutes>fortestingbot maestro,espressoandxcuitest: how long to wait for results, counted from when the tests start and shared by every--retryattempt. Default 60. -
--fail-fastfortestingbot maestro,espressoandxcuitest: at the first failure that will not be retried, the runs still queued or running are cancelled. The command waits for them to stop, then reports as usual and fails with exit code 2. -
--priority high|normal|lowfortestingbot maestro,espressoandxcuitest: where the runs go in your own queue while they wait for a free parallel slot. High starts before normal, normal before low, then oldest first. It does not take slots from other accounts or raise your parallel limit. Needs the matching API change; older API versions ignore it.
Changed
- When the wait for results times out (after
--timeout, or the default 60 minutes), the CLI now cancels the runs that are still queued or running, prints the results so far and exits with code 2 (outcome: failedwith anerrorin--json). Before, it exited with code 1 and left the runs going.testingbot status --waitstill only stops watching and leaves the runs alone.