<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: ashish004</title><link>https://news.ycombinator.com/user?id=ashish004</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 07 Apr 2026 23:40:43 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ashish004" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by ashish004 in "Show HN: Finalrun – Spec-driven testing using English and vision for mobile apps"]]></title><description><![CDATA[
<p>Just updated README.md, it's lot simpler and addresses on the core. Thanks for the feedback, please checkout</p>
]]></description><pubDate>Tue, 07 Apr 2026 22:59:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=47682423</link><dc:creator>ashish004</dc:creator><comments>https://news.ycombinator.com/item?id=47682423</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47682423</guid></item><item><title><![CDATA[New comment by ashish004 in "Show HN: Finalrun – Spec-driven testing using English and vision for mobile apps"]]></title><description><![CDATA[
<p>Yes gavinray, It gets persisted to the project. Its lives alongside the codebase. So that any test generated has the best context of what is being shipped. which makes the AI models use the best context to test any feature more accurately and consistently.</p>
]]></description><pubDate>Tue, 07 Apr 2026 18:37:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47679506</link><dc:creator>ashish004</dc:creator><comments>https://news.ycombinator.com/item?id=47679506</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47679506</guid></item><item><title><![CDATA[New comment by ashish004 in "Show HN: Finalrun – Spec-driven testing using English and vision for mobile apps"]]></title><description><![CDATA[
<p>Hi Avikaa, finalrun provides skills that you can integrate with any IDE of your choice. You can just ask the finalrun-generate-test skill to update all the test for your new feature.</p>
]]></description><pubDate>Tue, 07 Apr 2026 17:53:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47678902</link><dc:creator>ashish004</dc:creator><comments>https://news.ycombinator.com/item?id=47678902</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47678902</guid></item><item><title><![CDATA[New comment by ashish004 in "Finalrun – Spec driven testing using plain English and Vision for mobile apps"]]></title><description><![CDATA[
<p>We have built a QA agent that can understand your plain english intent and uses vision to reason and navigate the app to test your intent. You can check our benchmark here
<a href="https://finalrun.app/benchmark/" rel="nofollow">https://finalrun.app/benchmark/</a> and how we architected our agent for the benchmark <a href="https://github.com/final-run/finalrun-android-world-benchmark" rel="nofollow">https://github.com/final-run/finalrun-android-world-benchmar...</a>. Its all open source</p>
]]></description><pubDate>Tue, 07 Apr 2026 15:06:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=47676540</link><dc:creator>ashish004</dc:creator><comments>https://news.ycombinator.com/item?id=47676540</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47676540</guid></item><item><title><![CDATA[Show HN: Finalrun – Spec-driven testing using English and vision for mobile apps]]></title><description><![CDATA[
<p>I wanted to test mobile apps in plain English instead of relying on brittle selectors like XPath or accessibility IDs.<p>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.<p>The bigger problem showed up around how tests are defined and maintained.<p>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.<p>I then tried generating tests directly from the codebase (via MCP). That improved sync, but introduced high token usage and slower generation.<p>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.<p>I kept the execution vision-based (no brittle selectors), but moved test generation closer to the repo.<p>I’ve open sourced the core pieces:<p>1. generate tests from codebase context
2. YAML-based test flows
3. Vision-based execution across Android and iOS<p>Repo: <a href="https://github.com/final-run/finalrun-agent" rel="nofollow">https://github.com/final-run/finalrun-agent</a>
Demo: <a href="https://youtu.be/rJCw3p0PHr4" rel="nofollow">https://youtu.be/rJCw3p0PHr4</a><p>In 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.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47676044">https://news.ycombinator.com/item?id=47676044</a></p>
<p>Points: 22</p>
<p># Comments: 8</p>
]]></description><pubDate>Tue, 07 Apr 2026 14:33:48 +0000</pubDate><link>https://github.com/final-run/finalrun-agent</link><dc:creator>ashish004</dc:creator><comments>https://news.ycombinator.com/item?id=47676044</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47676044</guid></item></channel></rss>