-
Notifications
You must be signed in to change notification settings - Fork 157
Code Coverage missing for all but one file and it's listing the imports as missing coverage #62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So, a couple updates. First, the weirdness of it reporting imports as uncovered lines disappeared at some point. And in fact, the coverage is working well for all the files I have one directory down from components--but still not for the ones that are two directories down. |
I had a similar problem, I found this: vire/jest-vue-preprocessor#43 |
Hi, this issue is related to #32 (and I just fix this coverage issue). |
@butlermd I've removed cacheing in v2.1.1, can you see if this fixed your issue. |
I tried @barterr's suggestion to no avail (I also was missing the style tag in a few unneeded components, but it didn't change anything) and I updated to v2.1.1 per @eddyerburgh's request. No difference. |
I'm having the same problem. If for the date exists a solution, please share it. Thanks. |
same here. Strangely the reports of all the other files are existent as html files in subfolders. |
I've release 4.0.0-beta.0. Please use that version to see if it fixes the coverage issue. If not, please create a new issue with a runnable reproduction. This issue is being tracked in #56 |
I made sure I updated
vue-jest
andjest
to latest versions with no success.I have a file structure that looks roughly like this (abstracting the names to simplify)
In this case, all components are SCF
.vue
files andComponent1.vue
is the only one showing up in coverage. It looks like thisWhile the coverage looks like this
So, clearly, it's not reading this file correctly for coverage purposes.
This is my
jest.conf.js
. It's mostly the normal one generated byvue init
.The only thing strange I'm doing is putting my tests in the same folder as the files they're testing. It's unusual for jest and vue perhaps, but if anything, I'd expect it would give me too much coverage in the report, not too little.
The text was updated successfully, but these errors were encountered: