April 7, 2026

Robots write tests, humans write takes

Show HN: Finalrun – Spec-driven testing using English and vision for mobile apps

AI FinalRun writes app tests in plain English — devs cheer, skeptics circle

TLDR: FinalRun is an open‑source tool that runs mobile app tests written in simple English and kept beside your code. Commenters love the vision‑based approach but split over one big question: will the AI’s generated tests be saved in the repo, or is this another short‑lived demo trick?

FinalRun just dropped a command‑line tool that lets you write phone‑app tests in plain English and store them next to your code, and the internet immediately turned into a courtroom drama. Fans swooned over the “finally, no more brittle test scripts” promise, while others side‑eyed the AI magic. One user asked the obvious: how does this thing actually understand English? Another threw roses for the choice to open‑source it, calling it “agentic testing” done right. A third voice went full “industry therapy session,” praising the move to keep tests with the app code and use vision (screen understanding) instead of those break‑every‑update locators.

Then came the twist: a sharp skeptic quoted the team’s own words about keeping tests in sync and asked if the bot’s generated test code actually gets saved in the project. If not, he warned, we’re just kicking the can down the road — today’s demo becomes tomorrow’s flaky mystery. Cue memes about robots “finally finding the Login button” and jokes about brittle XPaths sounding like brittle exes. Meanwhile, the team’s docs stress sane basics (don’t commit secrets; use .env files), and there’s a slick demo video plus the site. Verdict from the crowd? Hopeful hype with a side of healthy paranoia — and they want receipts on test persistence.

Key Points

  • finalrun-agent is an AI-driven CLI for mobile app testing using repo-local YAML specs run on Android or iOS.
  • A one-line installer sets up Node.js (via nvm if needed), installs the finalrun CLI, adds skills for Claude Code/Codex, and guides platform tool setup.
  • Native driver assets are stored under ~/.finalrun/assets/<version>/ and run artifacts under ~/.finalrun/workspaces/<workspace-hash>/artifacts.
  • Workspaces use a .finalrun/ directory for tests, environment bindings, and config; secrets and provider keys must be stored in root .env files and gitignored.
  • CLI supports validation (finalrun check, doctor), executing tests/suites, and serving inspection reports; default env/model can be set in config with CLI flags taking precedence.

Hottest takes

"How does your agent understand plain english?" — arnold_laishram
"Using vision-based execution… but moving the test definitions to live directly alongside the repo context is definitely the real win" — avikaa
"If not, you have kicked the proverbial can down the road" — gavinray
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.