`test:cover` results in "No coverage information was collected, exit without writing coverage information" #245

dan-turner · 2016-08-25T00:09:48Z

Node version:
6.3.0
npm version:
3.10.3
Operating system:
OSX
Command line used:
zsh
Steps to reproduce:
npm run test:cover

The text was updated successfully, but these errors were encountered:

coryhouse · 2016-08-25T07:57:35Z

Can you try on the native Mac terminal? Runs fine for me there.

Mardaneus86 · 2016-08-25T13:54:36Z

Same issue here. When running on the native Mac terminal it gives no coverage information. However if I change the path to _mocha from /node_modules/mocha/bin/_mocha to just _mocha it does give coverage information.

Running the same on a windows machine (through VSTS, Visual Studio Team Service builds), it gives no coverage information either with the /node_modules/mocha/bin/_mocha path, but even crashes when I try just the _mocha part (as stated in the comments of PR #246).

So it seems the issue is not with the path to _mocha?

kwelch · 2016-08-25T14:16:26Z

Shouldn't node_modules, have a ./ before it?

Mardaneus86 · 2016-08-25T14:20:55Z

Made a mistake, it's node_modules/mocha/bin/_mocha, not /node_modules/mocha/bin/_mocha like I said in the previous comment. However, I don't think it's related to this specific part, but unsure what's causing it.

The test:cover:travis script is working, only difference with test:cover is that it just adds _mocha without the node_modules prefix.

kwelch · 2016-08-25T14:24:08Z

Right, does switching it to ./node_modules/mocha/bin/_mocha fix anything

Mardaneus86 · 2016-08-25T14:25:03Z

Negative. It doesn't break anything either, but still no coverage output.

markau · 2016-08-29T06:11:13Z

I assume you have unit tests defined? Sorry for the obvious question. remove-demo leaves only an empty placeholder emptyTest.spec.js.

Mardaneus86 · 2016-08-29T08:30:08Z

In my case, yes, I do have unit tests defined.

Mardaneus86 · 2016-09-06T18:00:30Z

Just did a clone of this project so I could check if it was related to my own project, but still getting the same result:

$ npm run test:cover

> react-slingshot@5.0.0 test:cover /Users/tim/Projects/react-sling-cover-test
> babel-node node_modules/isparta/bin/isparta cover --root src --report html node_modules/mocha/bin/_mocha -- --require ./tools/testSetup.js "src/**/*.spec.js" --reporter progress


  [▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬]

  54 passing (125ms)

No coverage information was collected, exit without writing coverage information

Really wondering what's the difference between node_modules/mocha/bin/_mocha and _mocha because that creates the following output, but it fails on Windows:

$ npm run test:cover

> react-slingshot@5.0.0 test:cover /Users/tim/Projects/react-sling-cover-test
> babel-node node_modules/isparta/bin/isparta cover --root src --report html _mocha -- --require ./tools/testSetup.js "src/**/*.spec.js" --reporter progress


  [▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬]

  54 passing (105ms)

================================================================================
Writing coverage object [/Users/tim/Projects/react-sling-cover-test/coverage/coverage.json]
Writing coverage reports at [/Users/tim/Projects/react-sling-cover-test/coverage]
================================================================================

=============================== Coverage summary ===============================
Statements   : 99.11% ( 779/786 ), 52 ignored
Branches     : 97.63% ( 247/253 ), 68 ignored
Functions    : 91.49% ( 172/188 ), 7 ignored
Lines        : 98.64% ( 509/516 )
================================================================================

techanvil · 2016-09-08T15:42:38Z

Just chiming in to say I am also experiencing this problem. Same version of Node/NPM as OP, running on Windows 10. I have just tested on a freshly pulled master.

If anyone has an old install which is working could you paste a snapshot of your installed node_modules versions?

ArcanisCz · 2016-09-15T07:40:26Z

It seems it broke with istanbul 0.4.5
douglasduteil/isparta#123
douglasduteil/isparta#126

I had similar problem on windows as you guys describe, and installing (--save-dev) istanbul 0.4.4 worked for me.

techanvil · 2016-09-15T08:41:42Z

Nice one @ArcanisCz, that works a treat!

coryhouse · 2016-09-15T13:03:51Z

Great find @ArcanisCz !

Hrmm, now question is, how can I fix this for everyone? Istanbul is not a direct dependency since Isparta merely uses it behind the scenes. So I believe we have to wait until either Isparta changes their reference or Istanbul fixes the bug.

And in other news, I'm strongly considering moving the project to Jest since it includes this built in and is generally now considered the best option for React dev.

kwelch · 2016-09-15T13:33:44Z

@coryhouse I am very interested in giving jest a try. Let me know if you want me to take a first pass on this?

Mardaneus86 · 2016-09-15T14:47:04Z

Setting the istanbul dev-dependency to 0.4.4 explicitly fixes the issue. @coryhouse: this might be a temporary fix for users of this project.

I'm also interested in seeing jest integrated.

coryhouse · 2016-09-15T16:19:22Z

@kwelch I'd love to see a PR on Jest! 👍

I'm eager to try it but have read enough to know it sounds like a slam dunk now.

oshalygin · 2016-10-23T04:10:41Z

+1 for you guys helping solve the issue and +2 for Jest. Possible Pluralsight vid on Jest in the future @coryhouse ? You talked about it quite a bit in the redux one but at that time it was still wonky 🗡

michaeljonathanblack · 2017-01-24T09:35:06Z

I am not able to see even the absent output. When I run npm run test:cover I run into an ELIFECYCLE error.

> babel-node node_modules/isparta/bin/isparta cover --root src --report html node_modules/mocha/bin/_mocha -- --require ./tools/testSetup.js "./{,!(node_modules)/**/}*.spec.js" --reporter progress


npm ERR! Darwin 15.6.0
npm ERR! argv "/Users/mherodev/.nvm/versions/node/v6.9.2/bin/node" "/Users/mherodev/.nvm/versions/node/v6.9.2/bin/npm" "run" "test:cover"
npm ERR! node v6.9.2
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE

ericcastro92 · 2017-01-25T00:32:15Z

I've been running in to the same ELIFECYCLE error as mherodev, is there any fix for this?

coryhouse · 2017-01-25T02:19:18Z

I am using Jest in my new course @oshalygin. I've lost patience with trying to keep code coverage working with Mocha. It just seems to be a house of cards. I'd like to move Slingshot to Jest since it has a much simpler config story, snapshot tests, and code coverage built in. I'd welcome a PR from anyone willing.

nickytonline · 2017-01-25T02:49:06Z

@kwelch, I guess that means you'll be looking at merging your Jest PR?

michaeljonathanblack · 2017-01-25T04:43:33Z

I was able to get coverage working in my own fork by making the istanbul version change, targeting mocha, updating istanbul.yml to exclude appropriate files and... maybe some other magic?

I'll see if I can get it working within this repository later tonight. Sorry for the wait.

If the migration to Jest isn't huge, I'd love to make it myself.

kwelch · 2017-01-25T04:59:40Z

@nickytonline I am looking to carve out time this week to wrapping that up. The tests run successfully, but output is still excessive and I have not touched coverage.

The branch is directly on this repo so PRs/commits to that branch are welcome with anything that will move the needle forward.

nickytonline · 2017-01-25T05:06:55Z

@kwelch cool beans. I have some free time this weekend, so I'll take a peek at the branch then.

michaeljonathanblack · 2017-01-25T12:10:01Z

I have a fix for the test coverage, but I can't seem to push to this repository.

mherold-mac:react-slingshot mherold$ git push
ERROR: Permission to coryhouse/react-slingshot.git denied to mherodev.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I made a fresh SSH key, pulled the repository, and it seems fine... outside of not being able to push, e.g.

Hi mherodev! You've successfully authenticated, but GitHub does not provide shell access.

coryhouse · 2017-01-25T13:40:29Z

Great to hear Michael! You can't commit directly - but you can submit a pull request.

…

On Wed, Jan 25, 2017 at 6:10 AM, Michael Herold ***@***.***> wrote: I have a fix for the test coverage, but I can't seem to push to this repository. mherold-mac:react-slingshot mherold$ git push ERROR: Permission to coryhouse/react-slingshot.git denied to mherodev. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. I made a fresh SSH key, pulled the repository, and it seems fine... outside of not being able to push, e.g. Hi mherodev! You've successfully authenticated, but GitHub does not provide shell access. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#245 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABnFpQzAOjzggs296CpRZ8u7zp0VpIRqks5rVzubgaJpZM4Jsk2J> .

-- Cory House bitnative.com <http://www.bitnative.com> Pluralsight Courses <http://www.pluralsight.com/author/cory-house> [image: https://mvp.microsoft.com/en-us/mvp/Cory%20House-5000840] <https://mvp.microsoft.com/en-us/mvp/Cory%20House-5000840>

kwelch · 2017-01-25T13:46:51Z

@mherodev There is a good egghead video by @kentcdodds if this is your first PR. 👍

michaeljonathanblack · 2017-01-25T19:42:06Z

I've committed thousands of PRs professionally, but this would likely be my first open source contribution 💃

For some reason, I cannot submit a new branch to this repository.

ERROR: Permission to coryhouse/react-slingshot.git denied to mherodev.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I'll see if that egghead video has any insight. In the mean time, should I not be using the ssh path to clone and push? I cleared out my ssh keys, generated a new one and added it to GitHub, but no dice.

Also, odd that it says could not read... I just cloned you, repo!

kentcdodds · 2017-01-25T19:43:22Z

You'll need to fork the repo. You'll learn about that in the course :)

michaeljonathanblack · 2017-01-25T19:44:10Z

Oh good, I'm glad I was doing it wrong. whew!

Edit: And hey Kent! Thanks for the video 💯

michaeljonathanblack · 2017-01-25T22:09:35Z

Got 'em: #358

Thanks for your help @kentcdodds, and @kwelch for the link.

kwelch · 2017-02-03T04:11:56Z

Closing this with the merge of #358.

Any further issues with test coverage, please refer to #223 or create a new issue. Thanks.

dan-turner mentioned this issue Aug 25, 2016

Fix test:cover task by removing extra path to _mocha #246

Closed

dan-turner changed the title ~~test:cover resulting in "No coverage information was collected, exit without writing coverage information"~~ test:cover results in "No coverage information was collected, exit without writing coverage information" Aug 26, 2016

kwelch closed this as completed Feb 3, 2017

kwelch mentioned this issue Feb 3, 2017

'open' is not recognized as an internal or external command, operable program or batch file. #350

Closed

shikhar-scs mentioned this issue Dec 19, 2017

Generate (test) coverage statistics mozilla/pdf.js#8632

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`test:cover` results in "No coverage information was collected, exit without writing coverage information" #245

`test:cover` results in "No coverage information was collected, exit without writing coverage information" #245

dan-turner commented Aug 25, 2016

coryhouse commented Aug 25, 2016

Mardaneus86 commented Aug 25, 2016 •

edited

Loading

kwelch commented Aug 25, 2016

Mardaneus86 commented Aug 25, 2016 •

edited

Loading

kwelch commented Aug 25, 2016

Mardaneus86 commented Aug 25, 2016

markau commented Aug 29, 2016

Mardaneus86 commented Aug 29, 2016

Mardaneus86 commented Sep 6, 2016

techanvil commented Sep 8, 2016 •

edited

Loading

ArcanisCz commented Sep 15, 2016

techanvil commented Sep 15, 2016

coryhouse commented Sep 15, 2016

kwelch commented Sep 15, 2016

Mardaneus86 commented Sep 15, 2016

coryhouse commented Sep 15, 2016

oshalygin commented Oct 23, 2016

michaeljonathanblack commented Jan 24, 2017 •

edited

Loading

ericcastro92 commented Jan 25, 2017

coryhouse commented Jan 25, 2017

nickytonline commented Jan 25, 2017

michaeljonathanblack commented Jan 25, 2017

kwelch commented Jan 25, 2017

nickytonline commented Jan 25, 2017

michaeljonathanblack commented Jan 25, 2017

coryhouse commented Jan 25, 2017 via email

kwelch commented Jan 25, 2017 •

edited

Loading

michaeljonathanblack commented Jan 25, 2017 •

edited

Loading

kentcdodds commented Jan 25, 2017

michaeljonathanblack commented Jan 25, 2017 •

edited

Loading

michaeljonathanblack commented Jan 25, 2017 •

edited

Loading

kwelch commented Feb 3, 2017

test:cover results in "No coverage information was collected, exit without writing coverage information" #245

test:cover results in "No coverage information was collected, exit without writing coverage information" #245

Comments

dan-turner commented Aug 25, 2016

coryhouse commented Aug 25, 2016

Mardaneus86 commented Aug 25, 2016 • edited Loading

kwelch commented Aug 25, 2016

Mardaneus86 commented Aug 25, 2016 • edited Loading

kwelch commented Aug 25, 2016

Mardaneus86 commented Aug 25, 2016

markau commented Aug 29, 2016

Mardaneus86 commented Aug 29, 2016

Mardaneus86 commented Sep 6, 2016

techanvil commented Sep 8, 2016 • edited Loading

ArcanisCz commented Sep 15, 2016

techanvil commented Sep 15, 2016

coryhouse commented Sep 15, 2016

kwelch commented Sep 15, 2016

Mardaneus86 commented Sep 15, 2016

coryhouse commented Sep 15, 2016

oshalygin commented Oct 23, 2016

michaeljonathanblack commented Jan 24, 2017 • edited Loading

ericcastro92 commented Jan 25, 2017

coryhouse commented Jan 25, 2017

nickytonline commented Jan 25, 2017

michaeljonathanblack commented Jan 25, 2017

kwelch commented Jan 25, 2017

nickytonline commented Jan 25, 2017

michaeljonathanblack commented Jan 25, 2017

coryhouse commented Jan 25, 2017 via email

kwelch commented Jan 25, 2017 • edited Loading

michaeljonathanblack commented Jan 25, 2017 • edited Loading

kentcdodds commented Jan 25, 2017

michaeljonathanblack commented Jan 25, 2017 • edited Loading

michaeljonathanblack commented Jan 25, 2017 • edited Loading

kwelch commented Feb 3, 2017

`test:cover` results in "No coverage information was collected, exit without writing coverage information" #245

`test:cover` results in "No coverage information was collected, exit without writing coverage information" #245

Mardaneus86 commented Aug 25, 2016 •

edited

Loading

Mardaneus86 commented Aug 25, 2016 •

edited

Loading

techanvil commented Sep 8, 2016 •

edited

Loading

michaeljonathanblack commented Jan 24, 2017 •

edited

Loading

kwelch commented Jan 25, 2017 •

edited

Loading

michaeljonathanblack commented Jan 25, 2017 •

edited

Loading

michaeljonathanblack commented Jan 25, 2017 •

edited

Loading

michaeljonathanblack commented Jan 25, 2017 •

edited

Loading