Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Vitest/C8 coverage includes the unit test files themselves
See original GitHub issueDescribe the bug
As per the docs I have the following npm script to generate the coverage report:
"coverage": "vitest run --coverage"
However it includes the unit test files themselves which is not useful and also leads to incorrect coverage metrics. Please can this be addressed in Vite?
Reproduction
Follow getting started guide and make a basic function and a unit test that imports that function. Have "coverage": "vitest run --coverage" in npm scrips and run it. Observe the reports in both the console and HTML istanbul report contain both SUT’s and the unit tests themselves.
System Info
Windows and Linux, Node 16.
Used Package Manager
npm
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It should already be excluded. We have
defaults.tsfile with default coverage. We need to addspecalongsidetestthere. PR welcome.Which begs the question, what happens if you do in-source testing? I love that feature, and I can’t leave it.