Integrations

Three kinds of integration

They are not variations on one thing, so it is worth knowing which one you are looking for before you pick a page.

Getting results out. GitHub Actions runs your test spec on a live device from a workflow and reports back on the pull request, so a regression blocks a merge rather than surfacing a week later. Slack puts the same results — plus visual regressions and quota warnings — in the channel your team already watches.

Getting your build in. React Native covers the live loop: your local Metro bundler attached to a cloud device, so a saved file shows up on the device a second later. Expo covers the EAS build profile that actually produces an uploadable artifact — and the one that looks right and is not. Flutter is the short one, because Flutter needs no special handling beyond building for the simulator.

Letting an agent drive. Claude Code — and Cursor, or anything else with terminal access — can install the CLI, run your app on a device and read structured results back, closing a loop that otherwise runs through you describing what happened.

If yours is not listed

It very likely still works. None of these are adapters we had to build — underneath every page on this list is a published command-line tool and a REST API. GitLab CI, CircleCI, Bitrise and Jenkins all run shell commands, which is the only requirement. The pages exist because each tool has its own quirks worth writing down, not because the others are unsupported.

The CI/CD integration guide is the place to start — it walks the whole pipeline from producing a build to reading results. The CLI reference covers every command and flag, and CI testing covers the test specification format.