nodejs / nodejs/node-addon-api
Improve coverage report with experimental runs
Open
Nobody has claimed this yet.
never-stale
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 499
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 2
Description
The CI job for coverage only runs for files under the npm test command. This does not include experimental builds, therefore code coverage reported in pull requests exclude those changes.
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 locating the CI coverage job and comparing the files included by the npm test command with the experimental builds. Determine how those experimental runs can contribute to pull-request coverage, then verify that coverage reports include changes exercised only by experimental builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100