-
Notifications
You must be signed in to change notification settings - Fork 87
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
Yet another "nothing covered" (with gulp-mocha 4.x) #115
Comments
+1. Both running istanbul from CLI or downgrading gulp-mocha to 3.x.x fixes the issue. |
I'm not sure how given the new gulp-mocha workflow you'd get this setup to work at all. You can write the covered files to disk so mocha read them, but then I'm unsure how you'd go about retrieving the coverage data who'll be local to the mocha process and unaccessible. |
The more I use Gulp, the less I can take advantage of its streaming possibilities 😥 |
To be honest with you, I'm really rarely using gulp anymore. I find it easier to use tools with more built in capacity - like jest for testing, webpack for compilation, etc. |
Finally fixed my issue by:
I still want to thank you @SBoudrias : your plugin has been very useful to me for a long time. Do I keep this issue open? French PS (off-topic) : idem de mon côté Simon, je me rends compte qu'au fur et à mesure mes builds Gulp ne font plus grand'chose qu'appeler des binaires CLI... Je songe sérieusement à me contenter des scripts NPM pour lancer mes opérations de build, Gulp n'étant devenu qu'une surcouche presque inutile. Même si je ne vais vraisemblablement plus utiliser |
I close this issue since the problem is not really related to this project. |
Otherwise no coverage reports are generated, see SBoudrias/gulp-istanbul#115
It appeared that gulp-mocha> 4.0 runs tests in a forked process so instanbul is not able to catch up coverage data See SBoudrias/gulp-istanbul#115
It appeared that gulp-mocha> 4.0 runs tests in a forked process so instanbul is not able to catch up coverage data See SBoudrias/gulp-istanbul#115
Mocha 4 doesn't work properly with code coverage via Gulp (SBoudrias/gulp-istanbul#115).
This issue is still referenced in the readme file, would be nice to keep it open or at least refer in the readme to the open issue in |
Unable to update past 3.0.1 due to change in gulp-mocha operation. see SBoudrias/gulp-istanbul#115 and sindresorhus/gulp-mocha#159.
Why is this still an issue? |
Locking conversation to prevent being spammed.
|
I'm using the "gulp-mocha" plugin to run my unit tests (which are ES6 modules processed by Babel). Everything worked fine until I decided to upgrade this plugin to the latest version (v4.0.0).
Now my coverage report is always empty. It seems that this new version of "gulp-mocha" does not play well with your plugin.
Any idea how I can restore the coverage report? Do you know any alternative?
I don't wish to downgrade the "gulp-mocha" plugin.
Here is my "gulpfile.js" (see the test tasks):
https://github.com/cedx/akismet.js/blob/master/gulpfile.js
The text was updated successfully, but these errors were encountered: