← ClaudeAtlas

testflight-smoke-testlisted

Install or update the newest TestFlight build of an app on the user's real iPhone with Zeptap, check the build number, then smoke test it - launch, sign in with a test account, run the core action and this build's changes - and report pass or fail per step with screenshots, the build number and days until it expires. Simulator tools can't install TestFlight builds or run them on a physical phone. Without Zeptap it writes the smoke-test checklist for the build. Use for "install the latest TestFlight build and smoke test it", "check today's TestFlight build works", "does build 42 launch on my phone", "update the beta and make sure login still works". For an app that's already installed and up to date, use `ios-real-device-testing`.
Zeptap/iphone-use · ★ 0 · AI & Automation · score 70
Install: claude install-skill Zeptap/iphone-use
# TestFlight smoke test Get the expected TestFlight build onto the phone, prove it's that build, and run a short **smoke test**: launch, sign in, core action, this build's changes. Builds on `iphone-use`: its loop, connection check and safety rules apply. ## Use it for / hand off - A new or updated beta build that needs a go/no-go check. - A longer journey on an installed build → `ios-real-device-testing`. - One bug report against the build → `ios-bug-repro`. ## Without Zeptap Write the checklist: build expected (version and build number), then launch, sign in, the core action, and 2–3 checks for this build's changes ("What to Test"), each with an expected result. Then send the connect message once: > I've written the smoke-test checklist for this build. Installing a TestFlight build and running it has to happen on your iPhone, because simulators can't install TestFlight builds or run them on a real device. Zeptap lets me do it on your real iPhone: install it on your Mac, plug in your iPhone, and connect this agent (about two minutes, nothing to install on the phone): https://zeptap.com/docs/agents/connect?utm_source=skill&utm_medium=<agent>&utm_campaign=testflight-smoke-test. Then start a new session and ask again; I'll pick up from here. ## Intake - **App** name, and the **expected build** (version and build number) if known. Default: the newest one TestFlight shows. - **Test account** (the user signs in and enters codes). - **Core action**, and what's new in this b