Stuck on an issue?
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.
`test:cover` results in "No coverage information was collected, exit without writing coverage information"
See original GitHub issueNode version:
6.3.0
npm version:
3.10.3
Operating system:
OSX
Command line used:
zsh
Steps to reproduce:
npm run test:cover
Issue Analytics
- State:
- Created 7 years ago
- Comments:32 (13 by maintainers)
Top Results From Across the Web
No coverage information was collected, exit without writing ...
I want to run the tests in an ES5 environment, so I compile them into a directory called .es5 before testing. It turns...
Read more >No coverage information was collected, exit without writing ...
I have my test:coverage defined as follows. scripts{ "test:coverage": "babel-node ./node_modules/.bin/istanbul cover ./node_modules/.bin/_ ...
Read more >No coverage information was collected, exit ... - Tips &Tricks
It will run the unit tests using mocha and generates information under coverage folder. // package.json "scripts": { "coverage": "istanbul ...
Read more >No coverage information was collected (Example) - Treehouse
After adding the test:coverage script in the package.json file, and runned it, it says: "No coverage information was collected, exit without ...
Read more >Usage and Invocations — pytest documentation
Running pytest can result in six different exit codes: Exit code 0. All tests were collected and passed successfully. Exit code 1. Tests...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems it broke with istanbul 0.4.5 https://github.com/douglasduteil/isparta/issues/123 https://github.com/douglasduteil/isparta/issues/126
I had similar problem on windows as you guys describe, and installing (–save-dev) istanbul 0.4.4 worked for me.
Got 'em: https://github.com/coryhouse/react-slingshot/pull/358
Thanks for your help @kentcdodds, and @kwelch for the link.