OpenZeppelin / OpenZeppelin/compact-contracts
Add code coverage
Open
Nobody has claimed this yet.
CI
stale
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
Investigate the current state of using code coverage with vitest (and/or other platforms). When integrated, there should be a separate script or flag that triggers code coverage output
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
Review how Vitest is currently configured and how the project’s tests are invoked. Investigate available code-coverage options, then integrate coverage so it can be triggered through a separate script or flag and produces coverage output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100