When to use Mo
Bug bash a release
Point Mo at a staging or preview build with the release scope. Mo plans the cases, runs them in parallel, and files the bugs it reproduced. Use it where the team has no suite for the pass and nobody free to run it by hand.Start a run from a prompt
Schedule repeated runs
Use a schedule for a nightly pass of the main flows. Each occurrence starts a new session from the same prompt. See repeat a session on a schedule.Run Mo on a pull request
With the Momentic GitHub App installed, Mo takes the preview URL for the branch and scopes the session to the change. Use it on every change, and keep a scheduled session for the wider coverage. See use GitHub context.What to point Mo at
Test a mobile app
Upload the build to a channel and tag as you do for a Momentic mobile test, then select it in the composer. Give no URL, and describe the flows and accounts instead. Mo installs the build on a remote simulator or emulator. See iOS app setup and Android emulators.Test from an existing spec or test plan
Start a session, upload the plan to it, then point Mo at the uploaded file:Use read-only repository context
Connect a GitHub repository, then name the change instead of describing it:Test a Vercel preview
Connect Vercel in settings > Integrations, leave deployment protection on, and give the preview URL in the brief:Test a local branch
Start a tunnel for the local branch:mo start, and keep http://localhost:3000 as the exact
URL in the brief. See
test a local build through a tunnel.
Some ways of running Mo are not available yet. See
not available yet.