trailofbits / trailofbits/anchor-coverage
"Per-function coverage could be a cool feature"
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 7
- Avg merge
- 10h 45m
- Merged PRs (30d)
- 10
Description
In a private communication, @Coriolan-dev wrote:
Now I just have a total coverage (60%).
But we could imagine to have the same data for each function so that you can easily see if a function is tested or not
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
The issue names no files, tests, or entry points. Start by mapping how this Rust wrapper around anchor test currently computes total coverage, then determine what per-function data and output should be supported. The work is ready only when the scope, expected results, and validation approach are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100