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.
Ask HN: How does your company balance test coverage and deploy speed? | Better HN
At Ubicloud, we have 100% line and branch coverage that is mandated on every PR (https://github.com/ubicloud/ubicloud). We also have an E2E test suite that we run periodically and with every commit. We did not really feel like our tests are slowing us down, it actually makes us faster since we have a higher trust to the payload and many manual checks that would need to be done is safely skipped.
