rust-lang / rust-lang/rust-clippy
Try using coverage tracking for Clippy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
It would be nice if we were able to gather test coverage information for Clippy.
We have an old script written by @mcarton that could be used to run kcov on Clippy. It seems like this script doesn't work currently for various reasons.
While making coverage tracking work again it might be worth to investigate tarpaulin, as well.
@felix91gr mentioned on Discord that they would like to work on coverage tracking once #3963 is done.
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 util/cov.sh and identifying why its kcov-based coverage run no longer works. Check whether tarpaulin is viable for Clippy, taking #3963 and the existing script into account; done means Clippy coverage information can be gathered again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100