ci: report coverage
Open
Nobody has claimed this yet.
needs discussion
priority-2-low
topic-tests
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
I think CI builds should report coverage (for code and tests), e.g. to codecov.io.
It might be as easy as using py-cov as a toxenv to enable it, and then upload it from there.
For performance reasons it should probably not done for all builds.
I'd be happy to provide a PR for it, but wanted to ask about / discuss it first.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by locating the repository's CI configuration and tox environments, then review how build jobs are selected. Confirm which builds should run py-cov and how coverage would be uploaded to codecov.io; done means an agreed, working CI report without adding coverage to every build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100