Running, debugging & the Test Console
Launch builds against detected simulators and emulators, and run your test suites with pass/fail parsing inside the app.
Last updated 2026-07-02
Beyond building for release, AppRelay helps you during development: launch a lane against a simulator or emulator, and run your test suites with the results parsed inside the app.
Run & Debug
The Run & Debug section detects the simulators and emulators available on your computer and lets you launch a lane against one of them. It uses the same toolchain the lane builds with, so an Xcode lane runs on an iOS Simulator, a Gradle lane on an Android emulator, and so on.
- Pick a lane. Choose which target you want to run.
- Pick a device. Select from the detected simulators/emulators — or a real iPhone or iPad, connected or paired over wifi.
- Run. AppRelay builds and launches, streaming the output so you can watch progress and spot errors.
The Test Console
The Test Console runs the test suites you define for a project and shows pass/fail without leaving the app. A test suite is just a labeled command plus how to interpret its result.
- Name
- What the suite is called in the UI.
- Kind
- A free-form label —
jest,xctest,gradle,pytest, or anything you like. - Command
- The command AppRelay runs.
- Working directory
- Where to run it, relative to the repo root.
- Pass signal
- How success is judged — an exit code, or a regular expression matched against the output.
Suites run through the same streaming process runner as everything else, so you see live output and a clear pass/fail at the end. Because the pass signal is configurable, AppRelay works with whatever your test runner prints — it doesn't assume a particular framework.
Where output goes
Runs, tests, and releases all stream their combined stdout and stderr into a live log with per-step markers, so a long build reads as a checklist rather than a wall of text. Optionally, test pass/fail history can be kept as part of a project's snapshots.