NewMCP server for Claude Code and Cursor

iOS testing at the speed of your coding loop

Describe a flow in plain English. TestedOK taps through it on your Mac's simulator in seconds and tells you the exact step that broke.

Free during beta: one app, 200 test runs a month · See how it works
testedok — tests/sign-up.json
❯ testedok run tests/sign-up.json
goal: “sign up with a new email and reach the home screen”
✓1Launch app2.8s
✓2Tap "Create account"0.5s
✓3Type email and password0.7s
✓4Tap "Continue"0.5s
✓5Check the home screen is showing0.4s
Tested OK · 5 steps · 4.9s

You ship faster than ever. Testing hasn't caught up.

Claude Code builds your app in a weekend. Nobody checks that sign-up, onboarding, and checkout still work after the 40th generated change. Manual tapping is tedious. Screenshot-based AI agents crawl, waiting on a large model at every step.

01
Describe the flow

Plain English, one sentence. No test code, no selectors, no recording.

“sign up with a new email and reach the home screen”
02
It runs on your simulator

TestedOK reads the accessibility tree and picks each tap in milliseconds. It falls back to a vision model only when unsure.

Accessibility treeFast decision modelVision fallback
03
Get pass or fail

With the exact failing step, in words your agent can act on.

✗ Step 3 tapped Continue, but the home screen never appeared

Seconds, not minutes.

Most agents screenshot every step and wait for a large model to reason about it. TestedOK works from the structured list of what's on screen, so a whole flow finishes before you switch tabs. Fast enough to run after every edit, not once per pull request.

Screenshot-based agent39.4s
TestedOK4.3s
Median time per test across 12 flows (Settings, Calendar, Reminders, and two of our own apps) on an iPhone 17 Pro simulator, September 2026. The screenshot-based agent is Claude Opus 5 looking at a screenshot every step.

Built for your coding agent

Claude Code and Cursor run your flows after every edit through the CLI or MCP server, read back the failing step, and fix it before you look up.

Claude CodeCursorMCPCLI
› I changed the onboarding screen. Running the flow.
❯ testedok run tests/onboarding.json
✓ 1 Tap “Get started” 0.6s
✓ 2 Type the email 0.7s
✗ 3 Tapped Continue, but the home screen never appeared
› Continue lost its action in my edit. Fixing ContinueView.swift and re-running.

Runs on your Mac

TestedOK drives the iOS Simulator you already have. No uploading builds, no device farm, no waiting in a queue.

Your build stays with you

Your app never leaves your Mac. To pick each tap, the model reads what's on screen as text. Screenshots go out only for the vision fallback and your run history, which keeps them for 30 days.

iOS-native

Built for SwiftUI and UIKit apps. Not a web tool with mobile bolted on.

Questions

Does it work with SwiftUI?
Yes. SwiftUI and UIKit apps both work.
What do I need?
A Mac with Xcode and the iOS Simulator. TestedOK is a single command-line tool; it sets up its simulator driver on first run.
What if my app has poor accessibility labels?
TestedOK falls back to a vision model for the steps it cannot resolve from the accessibility tree.
Do I need to write code?
No. Describe the flow in plain English, with the text you expect to see at the end.
Is it free?
Free during the beta: one app and 200 test runs a month.
What about Android?
Coming later. iOS first.

Ship the change. Know it still works.

Free during the beta: one app and 200 test runs a month. Sign up and run your first flow in minutes.