jlos

On one side good test coverage on PR's going into master and again when master goes live helps reduce incidents. But with enough tests, they become a bottle neck for releasing quickly.

So just curious what strategies you've seen in the wild for balancing test coverage* and deploy speed?

* By test coverage here, I mean how often to run the tests you have, not avoiding writing the tests in the first place.