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.
nyc mocha help needed
See original GitHub issueHello,
I have an issue that I cannot resolve without your help.
I am running mocha tests using chai asserts. When I run the test file using mocha, e.g: mocha test/cli-commands/coverage/coverage.js
The tests are running OK.
When I use
nyc --check-coverage --lines 95 mocha 'test/**/*.js' --require mocha.opts.helper.js
All the test are failing due to timeout or something else that I don’t understand.
What is the difference when I run the command with nyc and without nyc.
Do you have some special timeout that I can specify ?
Thank you.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 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
nyc adds instrumentation (hit counters) to your code so this could make the code take slightly longer than before. nyc does not impose timeout’s, this would be mocha. Possibly your timeouts are set with little margin of error and the instrumented code takes just too long.
That is all anyone can say without a minimal repository showing a reproduction.
Hi @ochikov can you please tell me how you overcame global window object issue while using nyc? I am facing the similar problem where my test cases are running with mocha but when I am using nyc with mocha, test cases are failing. I am using global window object.