Add code coverage check to PR build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 128
- Forks
- 110
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 10
Description
We currently use coverage tool to report the code coverage from unit and system tests. See
e.g:
https://github.com/ni/nimi-python/blob/266e87f372e27d4a05cbc637b0bbe8e5dc305726/generated/nidcpower/tox-system_tests.ini#L32
https://github.com/ni/nimi-python/blob/266e87f372e27d4a05cbc637b0bbe8e5dc305726/tox-travis.ini#L46
Logs:
- https://app.travis-ci.com/github/ni/nimi-python/jobs/576582446#L2052
- https://github.com/ni/nimi-python/runs/7326743697?check_suite_focus=true#step:3:1027
We should looking into setting a threshold and have the PR build fail if the coverage is below it.
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 coverage configuration in generated/nidcpower/tox-system_tests.ini and tox-travis.ini, then inspect the linked Travis and GitHub Actions logs to understand the current PR build. Determine how a coverage threshold should be applied to the existing unit and system-test reports, and consider the work done when a below-threshold PR build fails.
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
- Mostly clear
- Newbie friendliness
- 35/100