Asking for advice about how to handle pytest coverage especially with the

--changed-since

flag. We used to enforce coverage minimums because we could run tests per module in a monorepo, and determine the coverage percentage by that module. However, if multiple files have changed, and we rely on the --changed-since flag to run whatever tests we think we need to run, I’m not sure how to get a reliable measure of coverage. The only way I think we can do this is to run all tests and rely on caching for speed, along with

--coverage-py-global-report

Any other ideas?

The only way I think we can do this is to run all tests and rely on caching for speed, along with

--coverage-py-global-report

That's what we do in CI. Plug in a remote cache for speediestness