I like that. What I also do, is ensure test coverage is over 100%¹ for important parts. Important is designated through churn (if a file or class os changed on

I like that. What I also do, is ensure test coverage is over 100%¹ for important parts. Important is designated through churn (if a file or class os changed on every second commit, it must be important) and through domain knowledge (building a recipe app, then likely the Recipe is important). ¹ covered by unit tests, AND (partially) covered by integration AND by E2E tests.