Use cases

Where Swarmy fits

Every one of these starts the same way: point Swarmy at a web app or a mobile build, give it a goal or none at all, and read what comes back. The difference is what you are trying to get done.

Test a flow before release, without writing the test

Describe what a user should be able to do and let the agents do it.

You give

A web app or a mobile build and a goal in plain language: “check out as a guest,” “sign up and add a card.” No test scripts, no SDK.

You get back

The agents carry out the goal and explore the flows around it. Findings come back ranked and sorted into defects the app got wrong, friction that cost your users effort, and anything the evidence didn’t settle.

  • Plain-language goal
  • Web & mobile
  • Ranked findings

Map an app that has no test cases yet

Point Swarmy at the app and give it no goal at all.

You give

Just the app. With no goal, Swarmy scouts on its own, mapping every screen and proposing the journeys worth testing.

You get back

A living Test Atlas of the app, plus the things no script checks: dead buttons, NaN prices, placeholder text leaking into the UI, stale copyright years.

  • No goal needed
  • Scouting
  • Test Atlas

Re-run the same journey on a schedule, with no upkeep

Keep a passing run and let it repeat exactly.

You give

Any passing run. Promote it to a deterministic replay and schedule re-runs against the Test Atlas.

You get back

Classic-automation reliability with none of the upkeep, and no model call at all. Each new run starts from everything earlier runs learned, so runs get faster and cheaper the more you test.

  • Deterministic replay
  • Scheduled re-runs
  • No model call

Check a mobile build on a real device

Hand over an iOS or Android build and the agents tap and swipe through it.

You give

Your iOS or Android app. The agents drive it on a live device, handling permissions and popups along the way.

You get back

The same ranked findings as on web, and any flow you want to keep can be exported as a Maestro flow.

  • iOS & Android
  • Live device
  • Maestro export

Test a build that only runs on your machine

Staging behind a VPN, or a branch on localhost: nothing has to be deployed first.

You give

A web app reachable from your machine. Bundled Chromium runs locally, so localhost and VPN-only environments work as they are.

You get back

Agents click, type, and navigate every flow in Chromium, Firefox or WebKit, then promote what passes to a deterministic replay.

  • localhost & VPN
  • Chromium · Firefox · WebKit
  • Runs on your machine

Bring the suites you already have

Swarmy sits next to Maestro, Appium, or Cypress rather than replacing them on day one.

You give

Your existing Maestro, Appium, or Cypress suites. Import and export freely.

You get back

Hand Swarmy as much or as little control as you like. What the agents find can go back out the same way it came in.

  • Maestro
  • Appium
  • Cypress

These are the ways the product is built to be used, described in the same terms as the rest of this site. Runs against named applications go up here only when the team behind the app is happy for us to show them.

Book a demo →Back to home