Requirement (Gold level): The project MUST have FLOSS automated test suite(s) that provide at least 80% branch and 90% statement coverage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 548
- Forks
- 133
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
We agreed on #1175 to open an issue to follow up a discussion about it for Node.js (cc: @mhdawson @RafaelGSS)
The project MUST have FLOSS automated test suite(s) that provide at least 90% statement coverage if there is at least one FLOSS tool that can measure this criterion in the selected language.
The project MUST have FLOSS automated test suite(s) that provide at least 80% branch coverage if there is at least one FLOSS tool that can measure this criterion in the selected language.
Context
- Discussion during the last meeting (Minute 36:36)
- CII Best Practices: Test Statement Coverage 90%
- Team Discussion about 90%
- CII Best Practices: Test Branch Coverage 80%
- Team Discussion about 80%
- Codecov Report
Potential actions
- Research if we meet the requirements
- Include some automation (scripts?) to ensure that the coverage is not going down over the time
- Ensure that the JS tests related to c++ are included in the coverage
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 linked CII Best Practices criteria, the Codecov report, and the referenced team discussions to determine whether Node.js meets the 90% statement and 80% branch thresholds. Then assess the potential automation and whether JavaScript tests related to C++ are included; done means documenting the result and identifying any required follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript, node.js
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100