What’s still broken about testing workflows in 2025?
I’ve been talking to a lot of devs recently about how they approach testing in fast moving teams. The same pain points keep coming up.
• Writing tests takes forever.
• Maintaining them is even worse.
• CI passes, but bugs still make it to production.
• Visual bugs? Test suites usually miss them.
• Things break silently and no one notices until it’s too late.
We spend hours building safety nets that feel more fragile than helpful.
And most of the time, it's not your test suite that spots a bug. It's your PM. Or a user.
So I wanted to ask the community here:
What frustrates you most about testing right now?
Is it writing and updating tests?
Flaky runs that block deploys?
Coverage gaps in real user flows?
Or just getting anyone to care enough to write tests?
Would love to hear how others are dealing with this.
Appreciate any real-world insights you can share.
Replies
Hi Juan,
Thanks for bringing up such a crucial topic! I completely resonate with the pain points you mentioned. In my experience, the biggest frustration is the gap between what tests cover and real user behavior—test suites often focus on isolated components or functions but miss complex user flows and edge cases, especially in UI/UX. This leads to false confidence when CI passes, yet bugs slip through.
Writing and maintaining tests can be tedious, especially in fast-moving teams where priorities shift constantly. Flaky tests are another headache, causing deployment delays and eroding trust in the testing process.
One approach that’s helped my team is incorporating more end-to-end testing with real user scenarios combined with automated visual regression testing to catch UI glitches early. Also, fostering a culture where everyone—not just devs but PMs and designers—values and contributes to testing has made a difference.
Would love to hear what tools or practices others have found effective in bridging these gaps!