I’ve been using a python script that combines our existing gradle coverage tool with https://github.com/Bachmann1234/diff_cover to highlight any new lines in a commit that aren’t covered by unit tests, which has been very helpful in finding untested corners of big PRs (especially useful when lots of code is generated by bots). It occurs to me that this would also be useful as an opt-in GitHub action, maybe triggered by a specific label being applied to a PR. What do people think? Keeping it opt-in would be important I think as the reports can be noisy, and of course not all coverage gaps really need to be filled.
- Alan
