Ask HN: What's the best way to protect against regressions?

As the codebases I work in scale, I'm wondering how to think about finding & detecting problems to important business logic earlier on, ideally during development.

The main ways to protect against regressions that I know about are 1) having a large set of (mostly integration-level, for me) automated tests, 2) adding business metric monitors, and 3) periodic manual human QA. Wondering if there's anything I'm missing.

With a growing codebase, the number of tests written gets almost out of control, and it's unclear which are the important ones. I've also seen business metrics being recorded in a place that "misses a spot" or otherwise breaks independently of the actual thing it's measuring, too. And there's no way to know the human flows are operating at the right granularity.

Is this something everyone just figures out ad hoc? What am I missing?