[HN Gopher] Teaching Claude to QA a mobile app
       ___________________________________________________________________
        
       Teaching Claude to QA a mobile app
        
       Author : azhenley
       Score  : 48 points
       Date   : 2026-03-22 19:04 UTC (3 hours ago)
        
 (HTM) web link (christophermeiklejohn.com)
 (TXT) w3m dump (christophermeiklejohn.com)
        
       | devmor wrote:
       | Reading through this reminds me of how bot farms will regularly
       | consist of stripped down phones that are essentially just the
       | mainboard hooked up to a controller that simulates the externals.
       | 
       | When struggling with failing to reverse engineer mobile apps for
       | smart home devices, I've considered trying to set something like
       | this up for a single device.
        
       | maxbeech wrote:
       | the worktree discipline failure is the most interesting part of
       | this post to me. when claude is interactive, "cd into the wrong
       | repo" is catchable. when it's running unattended on a schedule,
       | you find out in the morning.
       | 
       | the abstraction is right - isolated worktree, scoped task, commit
       | only what belongs. the failure is enforcement. git worktrees
       | don't prevent a process from running `cd ../main-repo`. that
       | requires something external imposing the boundary, not relying on
       | the agent to respect it.
       | 
       | what you've built (the 8:47 sweep) is a narrow-scope autonomous
       | job: well-defined inputs, deterministic outputs, bounded time.
       | these work well because the scope is clear enough that deviation
       | is obvious. the harder category is "fix any failing tests" - that
       | task requires judgment about what's in scope, and judgment is
       | exactly where worktree escapes happen.
       | 
       | i've been working on tooling for scheduling this kind of claude
       | work (openhelm.ai) and the isolation problem is front and center.
       | separate working directories per run, no write access to the main
       | repo unless that's the explicit task. your experience here is
       | exactly the failure mode that design is trying to prevent.
        
         | cmeiklejohn wrote:
         | yeah, it's curious. I sometimes ask it why it ignored what is
         | explicitly in its memory and all it can do is apologize. I ask
         | -- I'm using Claude with a 1M context, you have an explicit
         | memory -- why do you ignore it and... the answer I get it "I
         | don't know, I just didn't follow the instructions."
        
       ___________________________________________________________________
       (page generated 2026-03-22 23:00 UTC)