It sounds like your software might be too complex and may benefit from being broken up into smaller, independent components. With a reasonably well-defined, de

It sounds like your software might be too complex and may benefit from being broken up into smaller, independent components. With a reasonably well-defined, decoupled system, you should be free to run a targeted test suite without much concern for affecting consumers (assuming you're not breaking contracts). Moving to CD(eployment) significantly reduced release complexity and increased quality of several of the system I owned in the past (which handled thousands of TPS and were affected millions of customers and dollars, globally, per day). In fact, I preferred starting with a CD pipeline to kick off new services from the start so from the very first check-ins (even before any tests were written), the deployment automation was in place and all changes were going to the latest stage we felt comfortable with at the time (often production, since initially there would be no consumers). That sets an expectation from the start that when developers peer review and merge, their code is going to production.