Skip to main content
Have Autosana verify that your code actually works — on your local iOS Simulator, Android Emulator, or web browser, against your dev environment with hot reload, no build uploads needed.

​
Prerequisites

  • Autosana MCP server added to your coding agent
  • One of:
    • iOS: macOS with a booted iOS Simulator
    • Android: macOS, Linux, or Windows with a booted Android Emulator
    • Web: a local dev server running on any OS (e.g. localhost:3000)

​
Usage

Tell your coding agent (Cursor, Claude Code, etc.): 
Test this new feature locally using Autosana
Everything else — CLI setup, dependencies, tunnel — is handled automatically.

​
Multi-Device Parallel Testing

Run the same flow across multiple devices at the same time — different screen sizes, OS versions, or just faster coverage.

​
How it works

  1. Boot your devices — open multiple iOS Simulators, Android Emulators, or both
  2. Tell your agent what to test:
Test my app on all my simulators in parallel
  1. The Autosana CLI auto-detects all booted devices, starts a separate session for each (with its own tunnel and Appium server), and runs your flows simultaneously across all of them
  2. Results come back per-device — you see pass/fail for each device independently, with links to the run details on the dashboard

​
What gets auto-detected

  • iOS: All booted Simulators (via xcrun simctl)
  • Android: All connected emulators and devices (via adb)
No manual device configuration needed — boot the simulators you want, and the agent handles the rest.

​
Example use cases

  • Screen size coverage: Run the same flow on iPhone SE, iPhone 16 Pro, and iPad to verify layouts across screen sizes
  • OS version testing: Boot simulators on iOS 17 and iOS 18 to catch version-specific bugs
  • Cross-platform: Test on both an iOS Simulator and Android Emulator in a single run

​
Close the Loop

The real power of local testing: your coding agent can build, test, and fix in a single loop. Give your coding agent a task — a feature, a bug fix, a ticket: 
Build <feature>. Test it locally using Autosana and fix anything that fails.
It writes the code, Autosana verifies it actually works on your simulator, and the agent fixes whatever breaks — looping until everything passes. With hot reload, the whole cycle takes seconds. 
Task
  ↓
Agent writes code
  ↓
Autosana verifies it on simulator/emulator/browser
  ↓
Pass → next task
Fail → agent reads results, fixes bug → ↑ retest