Improve code coverage accuracy
Open
Nobody has claimed this yet.
complexity:medium
stale
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
From #3223 - Codecov comments have been disabled since they're mostly noise until we can accuratly represent code coverage.
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
Start by reading the referenced issue #3223 and tracing how Codecov coverage is currently represented. The issue does not name files, tests, or an entry point; done means coverage is represented accurately enough that Codecov comments are no longer mostly noise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100