Opened 3 weeks ago
Last modified 2 weeks 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: | Accepted | |
| Has patch: | yes | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | yes |
| 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 (5)
comment:1 by , 3 weeks ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 3 weeks ago
comment:3 by , 3 weeks ago
(The linked implementation just treats that complexity as outside of MVP and makes this caveat explicit in the posted comment.)
comment:4 by , 3 weeks ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:5 by , 2 weeks ago
| Needs documentation: | set |
|---|---|
| Patch needs improvement: | set |
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
.coverageartifacts 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).