-
Notifications
You must be signed in to change notification settings - Fork 9
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
Server-side coverage is not tracked #3
Comments
No idea here! 😞 I looked for a relevant issue in https://github.com/cypress-io/code-coverage but didn't see any. It's possible this could be a mistake from Cypress's code-coverage module, from Istanbul, or from some aspect of the config written here. If you find the answer, let's definitely fix it here. |
I'll report it with them. |
The problem could be here, to be clear. I just don't see where. |
Same issue, any update about solution ? |
@bahmutov let me know if you have any ideas that I can act on - even if it's just high level thoughts. Would love to keep this repo working well and I can do a Cypress v10 update |
Hey!
Thanks for putting this together, I was able to adopt it for my project ❤️
However, I found that some files don't seem to be tracked, specifically anything that runs server-side. In my project, I have middlewares, api routes,
getServerSideProps
, etc... and all of that is not being tracked.I've put together a minimum example with a single
getServerSideProps
call.I made sure to explicitly
include
the file I want to cover in the.nycrc.json
file, however, code inno-coverage-here
is not being tracked as you can see:An interesting side note seems to be, that there invocation of
![image](https://user-images.githubusercontent.com/439587/165512469-91e713f3-4333-4e83-8a13-53421b0f95b8.png)
foo()
seems to be tracked correctly, it's really just the file insideno-coverage-here
that's missing.Any idea what could be going wrong here?
The text was updated successfully, but these errors were encountered: