How to compute coverage of new/modified code with grcov for rust？
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 170
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 4
Description
Many times, after a new code submission, I want to know which functions or lines's test coverage have been improved , or which new code is new commited and are not test. Does grcov support this? for example like diff-coverage-gradle or jacoco does.
Thank you very much.
Contributor guide
No contributing guide indexed for this repository
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 files, tests, or entry points are named in the issue. Start by reviewing grcov's current coverage collection and aggregation behavior, then determine whether changed-code coverage is supported and define what output should identify uncovered new or modified lines and functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100