Opened 2 hours ago
Last modified 88 minutes ago
#36620 assigned Cleanup/optimization
Automate test coverage check on pull requests
Reported by: | Jacob Walls | Owned by: | Saurabh |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
We could automate a significant part of checking test coverage on pull requests. Instead of using a cloud service, there's an implementation using diff-cover
in a PR.
Change History (3)
comment:1 by , 2 hours ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:2 by , 2 hours ago
comment:3 by , 88 minutes ago
(The linked implementation just treats that complexity as outside of MVP and makes this caveat explicit in the posted comment.)
Note:
See TracTickets
for help on using tickets.
I think the last time this was attempted the efforts stalled due the difficulty of combining coverage reports from different suite runs. Some part of the code is only covered by tests run on Postgres or a particular Python version for example so there needs to be a coordinated job that collects all of the
.coverage
artifacts and then combine them otherwise the resulting coverage report will be lacking or improperly reporting that some areas are not covered (e.g. if we only use the SQLite test run and Postgres only changes are introduced).