Skip to main content
The explore agent is in beta and may change.
Plenty of teams keep their Momentic tests in a repo of their own, separate from the application they cover. When the app source is not in the same repo as your tests, you can skip the diff entirely and have momentic ai explore map the running app instead. Run it on a schedule from the test repo and let it seed coverage. This is the simpler of the two poly-repo setups: one repo, no cross-repo checkout. If you want coverage tied to specific pull requests instead, see Explore a code diff into a separate test repo.

​
Run it

Build and start the app first and point the project’s baseUrl at it, since this is what the agent explores. Then, from the test repo:
explore latest maps the whole product and seeds coverage for it instead of anchoring to a change. --no-code drops the agent’s git and filesystem access, which it would otherwise waste looking for application source that is not in this repo; it grounds everything in the running app through its browser session.

​
Delivering the tests

Explore runs inside the test repo, so tests are written where git can see them and the On successful explore setting in Settings > Explore behaves like any single-repo run. Set it to pull-request to get a PR against the test repo. The CI guide covers the delivery options and a workflow you can adapt to a scheduled trigger.

​
Notes

  • Explore never touches your application code. Its analysis is read-only with respect to the app.
  • Because there is no diff, coverage grows as a baseline over the whole product rather than reacting to what just merged.