#36620: Automate test coverage check on pull requests
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Saurabh
Type: | Status: assigned
Cleanup/optimization |
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
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
[https://coverage.readthedocs.io/en/7.10.7/commands/cmd_combine.html 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).
--
Ticket URL: <https://code.djangoproject.com/ticket/36620#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019981e14115-cea8c1b3-004d-4919-8a92-d4e32f3b2493-000000%40eu-central-1.amazonses.com.
