Hey everyone, I’ve put together this blog post summarizing what I’ve learned over the past month while building a QA-focused startup. I’m still developing my understanding of the space, so I’m also looking for gaps I might be missing. All feedback is welcome!
The hardest part of QA still seems to be maintaining tests as the system evolves. Curious whether you’re aiming at test generation, test pruning, or improving test reliability.
> The hardest part of QA still seems to be maintaining tests as the system evolves
That’s interesting. It may explain why so many companies now push “self-healing” tests with LLMs for small UI shifts. The teams I spoke with faced different challenges, so the toughest part varied by where they stood in their QA cycle.
> Curious whether you’re aiming...
I started with a broad “AI test everything” approach, but I learned fast that the intent problem I mentioned is tough to beat. The prototype looked great in demos, yell fell short when I dogfooded them on my other projects. And when I met with teams, I didn’t see clear market pull. What comes next is still open.
blancotech|3 months ago
danishSuri1994|3 months ago
blancotech|3 months ago
That’s interesting. It may explain why so many companies now push “self-healing” tests with LLMs for small UI shifts. The teams I spoke with faced different challenges, so the toughest part varied by where they stood in their QA cycle.
> Curious whether you’re aiming...
I started with a broad “AI test everything” approach, but I learned fast that the intent problem I mentioned is tough to beat. The prototype looked great in demos, yell fell short when I dogfooded them on my other projects. And when I met with teams, I didn’t see clear market pull. What comes next is still open.