Test an iOS app and collect bugs automatically
Use Claude Code to drive an iOS app through its accessibility tree, visit screens, and return a structured bug report.
- What they did
- A developer used ios-builder from MobAI to connect Claude Code to an iPhone simulator or a real device. The setup handled the build in GitHub Actions, then Claude followed the accessibility tree and screenshots to tap buttons, fill out forms, and move through every screen and flow. After that, it checked the debug logs and wrote up the findings in a structured format.
- How it went
- In one demo, the run finished in eight minutes and surfaced every bug the developer had overlooked. It did this without any XCUITest scripts or prewritten test cases, and the writeup does not list bug totals or say whether any false positives appeared.
- Tips
- This is good for broad app coverage, but it still needs a working accessibility tree and a proper build setup. Check the ios-builder repository for installation details and constraints before depending on it.
Try it yourself with Claude Code
Open [iOS app project path] in [simulator or connected device] and explore the app end to end using the accessibility tree and screenshots. Tap through every reachable screen and flow, enter sample values in forms, and check debug logs for errors. For each issue, return a table with screen, exact steps, expected behavior, actual behavior, and severity. Before you do anything that would send data, make a payment, delete content, or submit a form, pause and ask me to approve that action. Do not change code; only test and report bugs. Stop when you have visited every reachable screen and flow, then give me a concise summary of the problems you found.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
1 more report of this
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Use Claude Code to plan and run a legacy stack migration
An engineer used Claude Code to map, split, and execute a multi-repo migration while keeping each step tied to docs, tickets, and review.
Review a pull request with staged sub-agents
Use parallel checks and a validation pass to review a branch or PR before you decide what to fix.
Use Claude Code to maintain NixOS server configs
A developer uses Claude Code to edit one NixOS config repo for several self-hosted machines, then reviews the diff and applies changes by hand.
Investigate why a service is getting killed
Run a read-only SSH check to find the cause of a process death and rank fixes by risk.
Audit CSS with MDN-backed browser checks
An MCP add-on let Claude Code look up MDN guidance and browser support while reviewing CSS for likely issues.
Run Microsoft Office on Linux with Wine
Use Wine and compatibility shims to get Microsoft 365 installing and opening on Linux without a virtual machine.