Authorization notice. DSH iOS is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA QA engineer testing a flow in an app who wants stable taps that do not depend on screen coordinates.
The problemCoordinate-based taps break when layouts shift, and manual testing is slow to repeat.
The outcomeThe agent taps elements by label or identifier and reports whether the expected text or state appeared.
What you need first
- A Mac, since the README says the tools fail with an explanatory error on non-macOS hosts
- DeepSeek Harness (DSH) installed, tested by the README with DSH 0.1.5-rc.1
- The npm package @zseven-w/dsh-ios, current plugin release 0.1.0-rc.10
- Xcode tooling for xcodebuild and simctl, which the build and simulator tools use
- For a real iPhone: a USB connection, the device unlocked, and Apple Development signing for device builds
Steps
- Call ios_sim_ui_tree on the booted simulator to list labels and identifiers on the frontmost screen.
- Call ios_sim_tap_element with the identifier or label of the control you want.
- Add expect_text or expect_gone to the same call so the tap and its check run in one round trip.
- If the tap is ambiguous, read the listed candidates and call ios_sim_tap_element again with a more specific identifier.
Prompt for your agent
Using the dsh-ios plugin in the ZSeven-W/dsh-ios repo, call ios_sim_tap_element on the simulator <udid> for the element labeled <label>, with expect_text set to <expectedText>. Report the expected.matched result and the screenshot path. Verify that expected.matched is true before you confirm the step passed.
Caveat. Taps match on label or identifier text, so apps with duplicate or unlabeled controls may return ambiguous matches that need a narrower identifier.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page