SaaS Metrics
I wanted to test mobile apps in plain English instead of relying on brittle selectors like XPath or accessibility IDs.With a vision-based agent, that part actually works well. It can look at the screen, understand intent, and perform actions across Android and iOS.The bigger problem showed up around how tests are defined and maintained.When test flows are kept outside the codebase (written manually or generated from PRDs), they quickly go out of sync with the app. Keeping them updated becomes a lot of effort, and they lose reliability over time.I then tried generating tests directly from the codebase (via MCP). That improved sync, but introduced high token usage and slower generation.The shift for me was realizing test generation shouldn’t be a one-off step. Tests need to live alongside the codebase so they stay in sync and have more context.I kept the execution vision-based (no brittle selectors), but moved test generation closer to the repo.I’ve open sourced the core pieces:1. generate tests from codebase context
2. YAML-based test flows
3. Vision-based execution across Android and iOSRepo: https://github.com/final-run/finalrun-agent
Demo: https://youtu.be/rJCw3p0PHr4In the Demo video, you’ll see the "post-development hand-off." An AI builds a feature in an IDE, and Finalrun immediately generates and executes a vision-based test for it verifying the feature developed by AI.
Show HN: Finalrun – Spec-driven testing using English and vision for mobile apps
A mobile app testing solution that overcomes brittle selectors and out-of-sync test flows by using vision-based agents and generating tests directly from codebase context for Android and iOS.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
A mobile app testing solution that overcomes brittle selectors and out-of-sync test flows by using vision-based agents and generating tests directly from codebase context for Android and iOS.
Finalrun tackles significant inefficiencies in mobile app testing by moving beyond brittle selectors and manual test maintenance. Its vision-based agent approach allows testing in plain English, improving robustness across Android and iOS. The core innovation lies in generating tests directly from codebase context, ensuring synchronization and reducing maintenance overhead, a common pain point with traditional test management. This 'post-development hand-off' where AI builds a feature and Finalrun immediately generates and executes a vision-based test demonstrates a highly automated, integrated QA workflow. For B2B SaaS, this offers a compelling solution for accelerating release cycles, improving test reliability, and reducing the cost of quality assurance, particularly in fast-paced development environments leveraging AI for code generation.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Finalrun – Spec-driven testing using English and vision for mobile apps?
Finalrun – Spec-driven testing using English and vision for mobile apps is analyzed by our AI as: A mobile app testing solution that overcomes brittle selectors and out-of-sync test flows by using vision-based agents and generating tests directly from codebase context for Android and iOS.. It focuses on Finalrun tackles significant inefficiencies in mobile app testing by moving beyond brittle selectors and manual test maintenance. Its vision-based ...
Where did Finalrun – Spec-driven testing using English and vision for mobile apps originate?
Data for Finalrun – Spec-driven testing using English and vision for mobile apps was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Finalrun – Spec-driven testing using English and vision for mobile apps publicly launched?
The initial public indexing or launch date for Finalrun – Spec-driven testing using English and vision for mobile apps within our tracked developer communities was recorded on April 8, 2026.
How popular is Finalrun – Spec-driven testing using English and vision for mobile apps?
Finalrun – Spec-driven testing using English and vision for mobile apps has achieved measurable traction, logging over 23 traction score and facilitating 10 recorded discussions or engagements.
Which technical categories define Finalrun – Spec-driven testing using English and vision for mobile apps?
Based on metadata extraction, Finalrun – Spec-driven testing using English and vision for mobile apps is categorized under topics such as: Spec-driven testing, English, vision, mobile apps.
What are some commercial alternatives to Finalrun – Spec-driven testing using English and vision for mobile apps?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Bluedot 2.1, which offers overlapping value propositions.
How does the creator describe Finalrun – Spec-driven testing using English and vision for mobile apps?
The original author or development team describes the product as follows: "I wanted to test mobile apps in plain English instead of relying on brittle selectors like XPath or accessibility IDs.With a vision-based agent, that part actually works well. It can look at the sc..."
Community Voice & Feedback
[dead]
Verification of AI generated code right would be dope.We do something similar in our company for web with playwright but facing a lot of flaky tests.Will check this out
I just ran my first test. Thanks team :)
Just updated README.md, it's lot simpler and addresses on the core. Thanks for the feedback, please checkout
> The shift for me was realizing test generation shouldn’t be a one-off step. Tests need to live alongside the codebase so they stay in sync and have more context.
Does the actual test code generated by the agent get persisted to project?If not, you have kicked the proverbial can down the road.
Does the actual test code generated by the agent get persisted to project?If not, you have kicked the proverbial can down the road.
[dead]
This solves a massive headache. The drift between externally generated tests and an active codebase is a brutal problem to maintain.Using vision-based execution instead of brittle XPaths is a great baseline, but moving the test definitions to live directly alongside the repo context is definitely the real win here.Did you find that generating the YAML from the codebase context entirely eliminated the "stale test" issue, or do developers still need to manually tweak the generated YAML when mobile UI layouts change drastically? Great project!
Agentic testing. Kudos to your decision to open-source it!
Looks pretty cool. How does your agent understand plain english?
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.