Back to browse
Spec-Driven Testing for mobile apps (preparing to open source)

Spec-Driven Testing for mobile apps (preparing to open source)

by arnold_laishram·Mar 16, 2026·2 points·0 comments

AI Analysis

MidBold BetShip It

Interesting concept, but landing page is broken and nothing is actually open source yet.

Strengths
  • Spec-driven approach avoids brittle XPath/ID locators that break in CI
  • Vision-based agent mimics human interaction rather than DOM dependency
  • Auto-generates edge-case specs from repo analysis with setup/cleanup
Weaknesses
  • Vercel security checkpoint blocks access — can't verify the actual product exists
  • Email collection form instead of working demo or code repository
Target Audience

Mobile app developers and QA engineers

Similar To

TestRail · BrowserStack · Applitools

Post Description

UI tests are brittle because they rely on fragile locators (XPaths/IDs). Tests pass locally but break in CI when UI IDs change — leading to constant maintenance and lost dev time.

Finalrun replaces locators with human-readable specs. You write plain-English instructions (e.g., “Tap Settings, search ‘Spanish’, verify ‘Español’”), and a vision-based QA agent drives the app visually like a human — so renamed IDs don’t break tests.

With plain english agent for testing mobile apps, Spec driven approach works smoothly without much maintainance: 1. With skills, The agent can analyze your repo, 2. Auto-generate edge-case specs (with setup/cleanup), and export them as .md tests 3. Now you can run the test via CLI (./mobile-cli run ./test/search.md).

If you want early access or the code when it’s open-sourced, I’m collecting emails: https://docs.google.com/forms/d/1EwHjqK6t1pBQgsKWih1Z_hQqP83...

(Also demo: https://youtu.be/SsVHRDWk_ss)

Similar Projects

Developer Tools●●Solid

Turn any OpenAPI spec into agent-callable skills

It extracts focused, executable operations from giant OpenAPI files (the GitHub REST YAML is shown) to shrink context and avoid sidecar adapter sprawl — a pragmatic answer to token bloat and brittle ad-hoc integrations. Useful and concrete: if it actually generates tidy, updateable skill units and runtime hooks it saves a lot of maintenance. That said, the idea competes with existing LangChain/openai-function patterns; the repo will need clear runtime, versioning, and update strategies to feel like more than a nicer converter.

Solve My ProblemNiche Gem
yz-yu
103mo ago