You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FAIL test\unit\specs\HelloWorld.spec.js
● Test suite failed to run
No file coverage available for: d:\tmp\test-jest2\src\components\HelloWorld.vue
at CoverageMap.fileCoverageFor (node_modules/istanbul-lib-coverage/lib/coverage-map.js:96:15)
at Array.forEach (<anonymous>)
Environment:
Windows 10 / Node 8.9.3 / NPM 5.5.1
Other Info
This broke over the weekend. It's not clear to me what changed so it seems likely to me this is really problem with one of this project's dependencies, but I could use a hand tracking down which one.
The text was updated successfully, but these errors were encountered:
Yea, I'm sure it is now. I was excited to start using Jest; it is much easier to setup than Jasmine or Mocha, so I was disappointed when it just stopped working.
Does this look like a Windows-only thing to you, or is it happening on other platforms?
I was able to throw a couple hours at this one today. I've got a successful (if limited) workaround and was able to determine that the issue was introduced with Jest v22.0.0. I also have some info that may help someone track this down or resolve; I posted them over at the Vue-Jest repo since I'm thinking that's where the fix will be.
Work Around
Place the Jest configuration directly inside package.json following the vue test utils jest-example. If you need any type of dynamic config obviously this won't be very helpful, but maybe it'll help someone.
Steps to reproduce:
vue init webpack jest-test
cd jest-test
npm run unit
Expected Result:
Tests pass with coverage report
Actual Result:
Tests fail with error:
Environment:
Windows 10 / Node 8.9.3 / NPM 5.5.1
Other Info
This broke over the weekend. It's not clear to me what changed so it seems likely to me this is really problem with one of this project's dependencies, but I could use a hand tracking down which one.
The text was updated successfully, but these errors were encountered: