How do small teams stop release testing from eating up all their dev time?
by•
Our dev cycle has turned into a endless loop of patching one bug only to watch another feature break right after.
It feels like we spend more time re-testing existing features than actually building new ones.
We’re trying to set up a lighter workflow so every update doesn't trigger a full manual check of the entire app.
What basic QA routines or lightweight tools keep your builds stable without slowing down your weekly ship date?
7 views
Replies
Hey Hugo,
have you ever thought why would a brand new feature break an existing one? Maybe there is a tight coupling somewhere that needs fixing?
Are these said fixes supposed to work/be-done in isolation (sounds about right to me)?
Are you using any automated tests - unit, integration, UI?
And last question - are you writing code yourselves or using agents?
And to answer your last question - if the code is not allowing isolated features/bugs to be implemented, then whatever the tools you use - you will be breaking it somewhere. Maybe the tools will show you faster, like if you have a UI-smoke-test set, but it won't prevent new bugs from being introduced.
I know that's probably opening more questions, but hopefully some of these could help you identify the root cause.
Cheers,
Ilian