Hello everyone,
I’ve spent years watching teams struggle with something that should be simple: trusting their tests.
On paper, everything looks fine.
The test suite is large. Coverage is high. CI is green.
But in reality?
Pipelines fail for no clear reason.
Tests break with small UI changes.
And teams hesitate when it’s time to deploy.
Not because they didn’t write enough tests but because maintaining them became the real problem.
This is something my brother and I have spent a lot of time thinking through and working on together.
That gap stuck with us.
So we decided to build something about it.
I’m a co-founder of GoQA AI, an AI-powered quality engineering platform focused on one thing: making tests reliable again.
We’re building a system that:
• Generates tests from user stories
• Runs them across web and APIs
• Adapts when the product changes (without constant rewrites)
No hype. No “AI replaces engineers” narrative.
Just solving a problem most teams quietly deal with: test maintenance.
We’ve started with web and API testing.
“Mobile is next”
Over the next few weeks, I’ll be sharing what we’re learning as we build:
→ How self-healing actually works
→ Practical ways to reduce flaky tests
→ Where AI helps and where it doesn’t
→ What building this in public really looks like
If your team has ever questioned whether failing tests actually mean something…
You’re not alone.
And it’s a problem worth fixing.
Curious to hear from others here, how do you deal with flaky tests today?
답글 남기기