Automate test coverage check on pull requests
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.
PR
Forum post
Change History
(11)
| Owner: |
set to Saurabh
|
| Status: |
new → assigned
|
| Triage Stage: |
Unreviewed → Accepted
|
| Needs documentation: |
set
|
| Patch needs improvement: |
set
|
| Needs documentation: |
unset
|
| Patch needs improvement: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Patch needs improvement: |
set
|
| Triage Stage: |
Ready for checkin → Accepted
|
| Patch needs improvement: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
| Patch needs improvement: |
set
|
| Resolution: |
fixed
|
| Status: |
closed → new
|
| Triage Stage: |
Ready for checkin → Accepted
|
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).