Unit tests check logic, snapshot tests detect output changes, and end-to-end tests verify predefined journeys—but unexpected behavior often appears outside those paths.
Exploratory testing: learning while interacting
Exploratory testing starts with a goal, not a fixed script. Each observation informs the next action, and unexpected behavior becomes a reason to investigate further.
An AI agent with access to an app's interface can follow this loop:
Observe → act → inspect → decide what to explore next.
The developer defines the scope. The agent chooses interactions, tries alternative paths, and documents potential issues. No predefined test flow is required.
Where it helps
- Broader feature coverage: Explore beyond acceptance criteria, including adjacent screens, interrupted flows, and unexpected state transitions.
- Varied action sequences: Reorder, repeat, cancel, and revisit interactions instead of following the same happy path.
- AI-assisted smoke testing: Check main screens and primary actions for obvious blockers after a new build.
- Recurring exploration: With external scheduling, revisit exploration goals across builds and collect observations for review.
- New regression cases: Turn confirmed discoveries into repeatable automated tests.
AI-Assisted Exploratory Testing Locally on iOS
iSimBot-MCP is an open-source tool that lets Claude Code, Codex, and other MCP-compatible agents see and control the local iOS Simulator.
It works with apps already installed in the simulator. No build-pipeline integration, in-app testing SDK, or source-code access is needed to explore the interface.
The agent drives the investigation through screenshots, taps, swipes, and text input. Known action sequences can also return multiple screenshots in a single call.
brew install wei0121/tap/isimbot-mcp isimbot setup Requires Apple Silicon, macOS 15+, and Xcode 26+ with an iOS simulator runtime. After setup, restart the selected client, connect to the simulator, and describe what to investigate.
The tool currently supports one selected iOS simulator per server. Build automation and recurring scheduling are outside its scope.
AI observations require human review: agents can miss issues or misunderstand intended behavior. Exploration complements existing tests; it does not establish that an app is bug-free.
Source code, demo, and installation instructions
Happy for any feedback.
