Code coverage, display 0% coverage for files not excluded
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 170
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
At the moment it seems like only the file used in kickcat unit are display in the coverage report. So a new file totally not tested is not reported as having 0% 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
No source file or test is named. Start by locating the code that generates the coverage report and the KickCAT unit-test or coverage configuration, then reproduce the report with an untested source file. Done means eligible, non-excluded files appear in the report with 0% coverage, with tests or a reproducible coverage check demonstrating that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100