Run tests

Run a Single TestCopy Anchor Link

Execute a test by name or ID:

revyl test run login-flow

The CLI will:

1. Resolve the test name (from aliases or API)
2. Queue the test for execution
3. Stream progress to your terminal
4. Report the final result and, for a blocking human-terminal run, open its report

Example OutputCopy Anchor Link

Running test: login-flow
Platform: android

Step 1/5: Tap the login button ✓
Step 2/5: Enter email address ✓
Step 3/5: Enter password ✓
Step 4/5: Tap Submit ✓
Step 5/5: Dashboard is visible ✓

Build: v1.2.3 from branch main
✓ Test passed in 45s
Report: https://app.revyl.ai/report/abc123

Run OptionsCopy Anchor Link

Blocking human-terminal runs open completed reports by default. --no-open, --no-wait, --json, --github-actions, CI, SSH, and other headless executions suppress browser opening.

Stored argument sets are flattened in attachment and flag order, followed by inline --launch-arg tokens in flag order. Explicit arguments precede iOS -KEY value pairs generated from environment configurations. Inline tokens are non-secret and can appear in shell history, process arguments, and reports. Android-only test runs reject iOS arguments with an actionable error.

Run a WorkflowCopy Anchor Link

Execute a workflow (multiple tests). To build, upload, and run in one command:

revyl workflow run smoke-tests --build

This builds your app, uploads it, then runs all tests in the workflow. Without --build, the workflow runs on its saved builds:

revyl workflow run smoke-tests

Example OutputCopy Anchor Link

Running workflow: smoke-tests
Tests: 5

[1/5] login-flow ✓ (32s)
[2/5] browse-products ✓ (28s)
[3/5] add-to-cart ✓ (41s)
[4/5] checkout ✗ (55s) - Validation failed
[5/5] logout ✓ (12s)

Results: 4 passed, 1 failed
Total time: 2m 48s
Report: https://app.revyl.ai/workflow-report/xyz789

Workflow OptionsCopy Anchor Link

Launch-configuration overrides apply to every compatible child test in the workflow. Mixed workflows apply iOS argument sets to iOS children and skip them for Android children.

Branch and build selectionCopy Anchor Link

A run uses the saved choice (the test's, or the workflow's App Override) unless you pass one for the run. On Default branch it tries your Git branch first. See How a run picks its build. The run prints its build and branch, such as Build: v1.4 from branch main, and a notice when it couldn't use your Git branch.

Tests created in the dashboard start on All branches · Latest build, so a pull request job can run another pull request's upload. Pass the ID of the build the job uploaded, or save the test on Default branch so it runs on the pull request's branch: revyl test build set <test> --build-selection inherit. See New saved choices.

revyl test build set <test> saves a test's choice, and revyl test build clear <test> resets it to All branches · Latest build. For how each run option behaves, including --build and per-platform overrides on workflows, see Run options.

Full Pipeline: Build → Upload → TestCopy Anchor Link

Use the --build flag with revyl test run to run the complete pipeline:

revyl test run login-flow --build --platform android

This executes:

1. Build - Run your build command
2. Upload - Upload the artifact to Revyl
3. Test - Run the test against the new build

Pipeline OptionsCopy Anchor Link

ExampleCopy Anchor Link

# Build Android, upload, and run test
revyl test run checkout-flow --build --platform android

# Run test without building (against existing build)
revyl test run checkout-flow

Full Pipeline: Build → Upload → WorkflowCopy Anchor Link

To build and run a workflow in one command:

revyl workflow run smoke-tests --build
revyl workflow run smoke-tests --build --platform android

This executes:

1. Build - Run your build command
2. Upload - Upload the artifact to Revyl
3. Workflow - Run all tests in the workflow against the new build

Leave out --build to run the workflow without rebuilding.

Workflow pipeline optionsCopy Anchor Link

Build or Upload Without Running TestsCopy Anchor Link

Upload a build without running tests:

revyl build --profile release --platform android

This builds in the cloud. Test/workflow --build remains local. See Build Configuration.

Upload OptionsCopy Anchor Link

Upload OutputCopy Anchor Link

revyl build upload --file ./app-release.apk --app <id> ends with the build and the branch it landed on:

Upload complete!
App:             <app-id>
Build Version:   feature-new-login-20260227-153000
Build ID:        <build-id>
Branch:          feature/new-login (Latest build: runs use this upload)
Package ID:      com.example.app

Build Version is the version label; Build ID identifies the build.

List BuildsCopy Anchor Link

View uploaded build versions across all branches of an app:

revyl build list --app "My App"

Options:

Without --app, the command lists app summaries. Cross-branch build tables show both GIT BRANCH and REVYL BRANCH (the dashboard's Branch column). See Upload and list builds for filters and JSON fields.

Exit CodesCopy Anchor Link

The CLI uses standard exit codes for scripting:

CI/CD ExampleCopy Anchor Link

#!/bin/bash
revyl workflow run smoke-tests

if [ $? -eq 0 ]; then
  echo "All tests passed!"
  ./deploy.sh
else
  echo "Tests failed, aborting deployment"
  exit 1
fi

JSON OutputCopy Anchor Link

For programmatic use, get structured JSON output:

revyl test run login-flow --json

{
  "success": true,
  "task_id": "task_abc123",
  "test_id": "test_abc123",
  "test_name": "login-flow",
  "status": "completed",
  "report_link": "https://app.revyl.ai/report/abc123",
  "duration": "45.0s",
  "error": "",
  "branch_name": "main",
  "build_version": "1.4.2",
  "build_id": "build_abc123",
  "branch_source": "default_branch",
  "git_branch_name": "feature-login"
}

branch_name, build_version, and build_id name the build the run used. branch_source says where its branch came from: git_branch, explicit_branch, or default_branch. git_branch_name names the Git branch the run consulted, so default_branch with a git_branch_name, as above, means your Git branch couldn't be used. See JSON fields. revyl workflow run --json reports these fields for each entry in tests.

Open Results in BrowserCopy Anchor Link

Blocking human-terminal test and workflow runs open the completed report by default. To state the intent explicitly:

revyl test run login-flow --open

Suppress browser opening with --no-open. No-wait, JSON, GitHub Actions, CI, SSH, and other headless runs never open a browser.

Or open a previous report:

revyl test open login-flow

Background ExecutionCopy Anchor Link

Queue a test without waiting for results:

revyl test run login-flow --no-wait

Output:

Test queued: login-flow
Task ID: task_abc123
Track progress: https://app.revyl.ai/task/abc123

Common WorkflowsCopy Anchor Link

Quick Smoke TestCopy Anchor Link

# Build, upload, and run workflow
revyl workflow run smoke-tests --build

# Or run workflow without rebuilding
revyl workflow run smoke-tests

Test New ChangesCopy Anchor Link

# Build, upload, and test
revyl test run login-flow --build --platform android

CI/CD PipelineCopy Anchor Link

# In your CI script
export REVYL_API_KEY=${{ secrets.REVYL_API_KEY }}

# Build, upload, and run the workflow on that build; fail the pipeline if tests fail
revyl workflow run regression --build --profile release --platform android --retries 2

Local Development LoopCopy Anchor Link

# Make code changes
# ...

# Quick test without rebuilding
revyl test run login-flow

# Full rebuild and test
revyl test run login-flow --build --platform android

TroubleshootingCopy Anchor Link

Cancelling a Running TestCopy Anchor Link

Use revyl test cancel or revyl workflow cancel to request cancellation of a running test or workflow:

# Cancel a running test
revyl test cancel <task_id>

# Request cancellation of a workflow and its tests
revyl workflow cancel <task_id>

Where to find the task ID:

• CLI output when starting a test: Task ID: abc123-def456...
• Report URL: https://app.revyl.ai/tests/report?taskId=abc123...

Test Times OutCopy Anchor Link

• Increase timeout: --timeout 900
• Check device availability in Revyl dashboard
• Verify the test runs manually in the web UI

Build Upload FailsCopy Anchor Link

• Check your build command produces output at the expected path
• Verify file permissions on the artifact
• Try --dry-run to see what would be uploaded

"Test not found" ErrorCopy Anchor Link

• Run revyl test list to see available tests
• Check spelling and case sensitivity
• Ensure the test exists in your config.yaml aliases or on remote