Anyone who's spent time managing automated tests knows the frustration of troubleshooting mysterious test failures. Hours spent sifting through logs, console outputs, network requests, and screenshots can grind productivity to a halt. We believe QA engineers and developers should focus their time on building and enhancing great software - not digging through logs. That’s why we built the Triage Agent: an intelligent assistant designed to pinpoint the exact cause of test failures using advanced large language models (LLMs). These models power most of the analysis, enabling adaptive, context-aware reasoning that mirrors how an experienced QA engineer would approach an investigation - but at lightning speed and scale.
Building a QA engineer
Software development is changing. The hype is deafening (I caught my grandma retweeting about vibe coding yesterday), but the changes are profound.
We’ve been busy building at Heal.dev, focusing on a mostly unloved part of software: quality assurance. We’re building a QA engineer.
Man, what’s gonna happen to UIs is insanely cool
I’m not a believer that chatbots will replace UIs completely. And that’s not because I doubt how crazy good chat interfaces are becoming, it’s because how appealing beautiful UIs are to us humans. GUIs did not kill terminals. But very few use only the command line, because UIs are nice to look at.
But how limited we are by our interfaces!
Most software products today use email verification and multi-factor authentication (MFA) to secure user accounts. This often ends up being a specific pain point for test automation.
Signup and login are critical failure points for any web application. Because they rely on third parties or shared states, authentication flows are hard to test with automated scripts. Some third parties also block browser automation. We've heard many stories of logins and signup flow breaking silently, and nobody noticing until analytics show a drop in user engagement.
At Heal, we believe that end-to-end tests should be as close as possible to the real user experience. In other words, they should replicate what a manual QA tester would do, including verifying emails and entering OTPs.
