paritytech / paritytech/revive
Code coverage
Open
Nobody has claimed this yet.
CI
- Dominant language
- Rust
- Stars
- 102
- Forks
- 26
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 6
Description
Generate code coverage reports (in README.md and as PRs comments). Start with the integration tests, (once ready, the E2E validation testing suite should be used to paint a more complete picture). Requires support in the LLVM build.
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
Start by reviewing README.md, the integration tests, the E2E validation testing suite, and the LLVM build support. Determine how coverage should be generated and published in the README and PR comments. Done means integration coverage is reported, with a path for later E2E coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, compilers, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100