standardize code coverage
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
At the moment our code coverage and testing story is weird/unkept. We should endeavor to adjust the codecov config to accomplish:
- diminish tracking of
ptd/ptdpython-based coverage - ensure go paths are tracked
- set a good minimum coverage percentage and actually reject PR merges if they cause it to drop below
- set a good minimum change for a given PR so one-liners or dumb changes don't fail cov test
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 locating the repository's Codecov configuration and CI coverage checks; no specific files or tests are named in the issue. Review how Python coverage under ptd/ptd and Go paths are currently tracked, then define thresholds and PR enforcement so coverage drops and insignificant changes are handled as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100