How is this different from coding agents like Claude Code that test apps?

Coding agents generate Appium/Maestro tests that still rely on brittle selectors and stay flaky. FinalRun uses a vision-based QA agent that tests like a human, making runs more robust and able to catch UI/UX issues as well.

Do I need to maintain locators or test scripts?

No. Tests are vision-driven and adapt to UI changes automatically.

Can I run on both iOS and Android?

Yes. Author once and run on iOS and Android devices locally and when you are ready to scale run in our cloud.

How do I trigger tests?

Kick off runs from CI/CD (GitHub, Jenkins, or webhooks) or on-demand from the dashboard.

How are results reported?

Each run ships video, logs, and bug analysis to Slack or email with links to failing steps.

What about backend steps?

True end-to-end: we validate app flows plus backend/API outcomes in the same scenario.

iOS App Testing From Claude — Simulator Runs Your Team Can Actually Repeat

If you already build features with Claude (Claude Code or API workflows), mobile app testing should live in the same loop — not a separate spreadsheet handoff. From SwiftUI to UIKit, App Store review and user trust depend on flows that work across screen sizes and permission dialogs.

What to ask Claude to do with FinalRun

Install FinalRun from the official script and scaffold .finalrun/config.yaml
Generate YAML specs from your feature folders
Run /finalrun-test-and-fix so failures produce actionable diffs

FinalRun: iOS testing that fits how you already build

FinalRun demo — AI-powered iOS app testing

FinalRun is a free, open-source CLI for iOS apps. You describe flows in plain English using YAML steps; an AI model drives iOS simulators and devices using vision, which reduces time spent maintaining brittle selectors.

Skills align with Claude Code slash-command habits
Narrow fixes: app vs test classification on each failure

Works with AI coding agents (Cursor, Claude Code, Codex, Google AntiGravity)

Install once, then stay in your agent session:

curl -fsSL https://raw.githubusercontent.com/final-run/finalrun-agent/main/scripts/install.sh | bash

Generate tests from your repo:

/finalrun-generate-test Add YAML coverage for the main user journey — include edge cases

Run tests and auto-fix failures:

/finalrun-test-and-fix Verify the critical flow end-to-end on iOS

Your agent can scaffold .finalrun config, organize tests by feature, read reports (screenshots, video, logs), and narrow fixes to application code versus test specs.

Get started on GitHub · Documentation · Community

Or Set It Up Manually

Prefer to manage your FinalRun workspace and test scripts yourself? Here is how.

Configure your workspace — create a .finalrun/config.yaml in your project:

app:
  name: MyApp
  packageName: com.example.myapp
  bundleId: com.example.myapp

Write tests in plain English — save YAML files in .finalrun/tests/. Each file describes one user flow to test.
Run:

finalrun test tests/registration.yaml

FinalRun launches your app on an emulator or simulator, executes each step using AI vision, and generates a detailed report with pass/fail status, video recording, and step-by-step screenshots.

Works with Every Mobile Framework

FinalRun's AI vision approach means it works with any app, regardless of how it was built:

Native Android (Kotlin, Java)
Native iOS (Swift, SwiftUI, UIKit)
React Native
Flutter
Expo
Kotlin Multiplatform
Ionic and Capacitor

Since the AI looks at pixels, not code, it does not matter what framework generated the UI.

CI pipelines and reproducible runs

Treat FinalRun like any other CLI in continuous integration: pin tool versions, upload report directories as workflow artifacts, and associate each run with a commit SHA. For iOS apps, document which emulators or simulators you use (and, on Android, how ADB connects to devices) so local runs match CI. Readable runbooks help new contributors reproduce failures without guessing.

What quality means for iOS apps

Quality goes beyond a green build: functional correctness, resilience on bad networks, accessibility (large text, screen readers), and observability when something breaks. Spend E2E budget on authentication, payments, permissions, and deep links — the flows that cost you users when they fail.

Ownership and triage

Treat FinalRun specs like application code — review them in PRs and update expected_state when navigation changes. Video shows gesture timing, screenshots show UI state, logs show crashes. Use those artifacts in triage instead of piling on retries.

Security and test data

Use sandbox accounts, synthetic data, and secrets managers. Never embed API keys in YAML. Redact tokens from shared artifacts.

Feature flags and parity

Document which flag state each spec assumes. If you ship on both Android and iOS, note where journeys must match and where differences are intentional. Pin SDK levels, system images, and CLI versions so failures are reproducible.

Before you merge

Config and tests live in version control beside application code
Steps describe user-visible copy, not internal element IDs
CI uploads artifacts tied to commit SHAs
Triage failures with video first, then logs
Secrets never appear in checked-in YAML

Frequently asked questions

Does Claude run the emulator for me?

Claude drives commands in your repo; FinalRun executes tests locally or in CI. Together they close the loop from intent to green run.

Is this only for experts?

No — readable YAML steps help ICs and QA align on what “pass” means.