Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Love your approach to product. It feels like TesterArmy will become the "Vercel for testing". Refreshing stuff!
  • Some digging FAST_MODEL = "google/gemini-3-flash" (fast mode primary) DEEP_MODEL = "openai/gpt-5.4" (deep mode primary) VISION_CLICK_MODEL= "openai/gpt-5.4" (the visual grounder)

    fast: gemini-3-flash, falls back to gpt-5.4, 15-min run timeout, max 2 visual calls/step. deep: gpt-5.4, 15-min timeout, max 3 visual calls/step.

    Why such a hard timeout, and why not latest models?

  • Was writing E2E tests ever a problem that needs automation? Also E2E tests need to be updated everytime a new feature is added. TesterArmy sounds great. But config overhead and potential security leaks makes it a no go
  • Have you been able to nail down a loop where your tool can take an open pr, guess the code path and do some testing?

    We use cypress heavily for our core flows which has a similar ai prompt thing but it’s not quite ad hoc enough for smaller fixes which is where the bottleneck still comes in for us.

  • On the mobile side, what's your strategy for state across cold starts? Agentic test runs tend to fall over the moment auth tokens expire mid-flow, because the agent has no notion of 'this state should persist across this device reboot but not that one'. Curious how you handle keychain/secure-storage in your test rigs.
  • Has anyone tried to build their own version of this?

    It's cool, but I'm not super excited about using some 3rd party SaaS as a critical part of my testing.

  • "Traditional E2E tests are slow to set up and expensive to maintain." I don't really understand this. If I'm already using Opus to write the code, surely it would know best what E2E tests to write to be able to verify its own output? This seems like an unnecessary external step.
    by dbbk
  • E2E tests are now quick to write due to LLMs, and are then deterministic AND cheap to run. How would this compare to the token costs of running an agent the whole time for each test? How do you make sure results stay stable regardless of the nondeterministic nature? Do customers still need to create test cases - any way to import from test case management system - based on which they could have already generate e2e tests locally?

Explore Birbla archives