From a scaling perspective, the Beyoncé Rule implies that complicated, one-off bespoke tests that aren’t triggered by our common CI system do not count. Without this, an engineer on an infrastructure team could conceivably need to track down every team with any affected code and ask them how to run their tests.
There are unmentioned / hidden caveats here:
1. All tests affected by the infra change must be run. That scales super-linearly.
So, then you have to set up a system to determine what to test depending on what changed. That's an investment/cost to consider.
2. Is that system right often enough? You/Google may get it right 99% of the time, but what about the other 1%? This can result in more user-facing breakages (not protected by tests). Is that okay (a trade-off you're okay with)? There are many cases where they are not, often products that users or companies pay for, software that's distributed and harder to quickly deploy fixes for, etc..
