0% code coverage with Quasar (Vue.js) and Cypress #20238
Unanswered
maiolica
asked this question in
Questions and Help
Replies: 2 comments
-
From what I understood, 0% coverage can happen either when the code hasn't been correctly instrumented or when the code isn't actually used in the run (eg. typescript or webpack dropped it since it wasn't used anywhere) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Just published oob code coverage support for Cypress + Vite + Quasar, check it out: https://github.com/quasarframework/quasar-testing/releases/tag/e2e-cypress-v4.1.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everybody, I've some issues instrumenting Vue.js components in Quasar.
https://github.com/maiolica/quasar-2-test-coverage
In this repo I've set the default Quasar 2 installation with Cypress e2e tests and the the Cypress code coverage plugin, but it seems .vue files are not instrumented correctly, may someone help me?
This issue seems similar to: istanbuljs/nyc#1366
Default setting:
Tweaked .nycrc settings for including .vue files
Beta Was this translation helpful? Give feedback.
All reactions