Infrastructure

By default, tests run wherever you run the CLI: a local browser for web, or a local emulator or simulator for mobile. As an option, Momentic can run them on managed infrastructure instead: hosted browsers and remote emulators and simulators, provisioned on demand, so you do not have to set up or maintain them yourself. This page covers where tests can run and how to choose.

​

Web browsers

Web tests run on a Chromium-family browser. Choose Chromium, Google Chrome, or Chrome for Testing per project or per test, and Momentic applies the same runtime overrides (user agent, viewport, and similar) on every run so results match between machines. By default the browser runs on your own machine or CI runner, with hosted browsers as an option. See browsers for the full list and how to set a default.

​

Remote emulators and simulators

As an option, mobile tests run on emulators and simulators hosted by Momentic. Instances are provisioned on demand, typically boot in under a second, and each test gets a fresh instance so state does not carry over between runs.

• Android: remote emulators provisioned by Momentic. See emulators.
• iOS: remote 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.

​

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 caller’s IP.

​

Running locally

Running on your own machine is the default: a local browser for web, a local AVD for Android, or a local Xcode simulator for iOS (macOS only). Local runs are useful for fast feedback while authoring. See running locally, and the Android and iOS pages for the local setup of each.

​

Next steps