Skip to main content
Momentic can provision browsers, Android emulators, and iOS simulators on demand so you do not have to set up and maintain them on your own runners.

Hosted Chrome browsers

Offload browser execution to Momentic-managed infrastructure to run tests with unlimited concurrency. Because your CI machines do not need to host the browsers, you can use lower-spec machines and reduce CI compute costs. Hosted browsers apply to momentic run only, locally and in CI. The editor and the MCP server run tests in a local Chromium, so keep it installed for authoring. Turn hosted browsers on for a project with browser.remoteBrowser:
momentic.config.yaml
With parallel: auto, momentic run sizes its worker count for hosted browsers (cores * 4 - 2). See parallel. Choose Chromium, Google Chrome, or Chrome for Testing per project or per test. Momentic applies the same runtime overrides, including user agent and viewport, on every run. See browsers for the full list and how to set a default.

Remote emulators and simulators

Mobile tests can run on emulators and simulators hosted by Momentic. Instances are provisioned on demand, boot in under a second, and each test gets a fresh instance so state does not carry over between runs.
  • Remote Android emulators provisioned by Momentic. See emulators.
  • Remote iOS simulators provisioned by Momentic. Real devices are not supported. See simulators.
Pick remote or local per test through the Region dropdown: any Momentic region selects remote, Local selects local.

App assets: channels and tags

Remote emulators and simulators install your app from build artifacts organized into channels (release environments like dev, staging, production) and tags (versions within a channel). A single channel/tag pair can hold both an Android APK and an iOS .app. Upload from the Momentic dashboard’s Assets page or with momentic-mobile assets. A tag is immutable, so if your tests should follow the latest build, upload with --alias nightly instead. An alias points at one tag within a channel, and a later upload can move it to a new tag. A test’s Tag or alias setting accepts either, and updating the alias’s tag moves every test that uses it without any test edits.

Regions

Set the Region in each test’s settings to choose which remote region runs it. If unset, Momentic picks the region closest to the machine running the CLI. The region is a preference and may fall back to other regions when capacity runs out. To pin emulators to a single jurisdiction (us, eu, or as) for data residency, set emulator.jurisdiction in momentic.config.yaml.

Next steps

Browsers

Supported web browsers and runtime overrides.

Android emulators

Remote and local Android emulators.

iOS simulators

Remote and local iOS simulators.

Run in CI/CD

Run tests on every commit and pull request.