-
Notifications
You must be signed in to change notification settings - Fork 784
Can't get coverage output #197
Comments
I am getting this on a new machine setup as well. The same commands that work on other machines are producing no output on this new machine. Windows 7 with node.js 0.10.28 |
So I figured out my issue: I was using my command prompt within a NTFS junction and when istanbul builds the file list, it uses |
+1 on ubuntu here. Istanbul doesn't correctly execute the |
Since #219 is merged, could you please retry with the latest istanbul and see if the issue goes away? |
@gotwarlost Considering the tests over at https://github.com/raszi/node-tmp which use both mocha and istanbul for coverage, everything works as expected. I believe that you can close this issue for good. |
I put istanbul into place a few weeks ago to cover our mocha tests and it's been awesome, but then all of the sudden I have noticed it is no longer producing new coverage output. When I run
istanbul -v cover _mocha -- --recursive tests
I get an empty coverage folder. Any ideas of how to debug this? I simplified my tests down to a single test case and the same thing happens.The text was updated successfully, but these errors were encountered: