Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
1–10 of 10 posts
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#2CI with regular e2e tests usually gets pretty expensive and slow. How does cost compare to regular playwright tests?
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#3I dont this is top most priority. We do this with codex or claude in chrome and validate the UX.
I think BDD is going to be back in style for agent generate code.
When you generate at scale discovering, maintaining and scaling test is the major problem, thats why were katana [1] a behavior driven testinf utility thay discovers behavior and maintain, generates test cases.
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#4"It reads the screen, not the DOM", but is built completely on Playwright? At first it made me think you have some visual model at play, but doesn't actually seem that way.
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#5We built something like this haha
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#6CI with regular e2e tests usually gets pretty expensive and slow. How does cost compare to regular playwright tests?
Argus adds one more layer onto Playwright, so we expect it to be slower. Think of it as a kind of tradeoff where you gain human-level QA by accepting slower runs.
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#7"It reads the screen, not the DOM", but is built completely on Playwright? At first it made me think you have some visual model at play, but doesn't actually seem that way.
yes, It uses gemini vision models on top of playwright
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#8We built something like this haha
can you share with us if It's public?
Re: Show HN: Argus, agentic QA for teams whose coding agents move faster than QA
#9I dont this is top most priority. We do this with codex or claude in chrome and validate the UX. I think BDD is going to be back in style for agent generate code. When you generate at scale discovering, maintaining and scaling test is the major problem, thats why were katana [1] a behavior driven testinf utility thay discovers behavior and maintain, generates test cases. [1] https://github.com/adaptive-scale/katana
cool project but, It's not always code that's broken.
Imagine you have a discrepancy in DB level that ends up with an error in frontend.
You always need real QA tests to ensure things are working smoothly.