Code coverage
Open
Nobody has claimed this yet.
starter-task
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
perhaps use https://www.npmjs.com/package/nyc which I just learned about from @tmcw (https://github.com/mapbox/tilelive.js/issues/138)
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 reviewing the repository's existing test setup and the nyc package linked in the issue. Done should mean that code coverage is added to the project's test workflow, but the issue does not specify files, commands, or coverage criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100