This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Lewis Ball
Recipients Lewis Ball
Date 2020-05-02.01:11:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588381882.86.0.0551558198731.issue40474@roundup.psfhosted.org>
In-reply-to
Content
The current reported code coverage stats on codecov.io miss some global statements of modules imported before coveragepy begins. This is documented in the dev guide, and the suggested fix is here: https://devguide.python.org/coverage/#coverage-results-for-modules-imported-early-on but that recommended fix doesn't seem to be included in the CI.

Using the recommended 'hack', the coverage report shows an extra 4k lines are coverage in Lib, increasing coverage percentage by around 3%. 

Having a more accurate view of the coverage makes it much easier to see which parts of the code need help with tests, without having to go into every individual report to see if global statements are misreported.

I'll raise a PR for this shortly
History
Date User Action Args
2020-05-02 01:11:22Lewis Ballsetrecipients: + Lewis Ball
2020-05-02 01:11:22Lewis Ballsetmessageid: <1588381882.86.0.0551558198731.issue40474@roundup.psfhosted.org>
2020-05-02 01:11:22Lewis Balllinkissue40474 messages
2020-05-02 01:11:22Lewis Ballcreate