-
Notifications
You must be signed in to change notification settings - Fork 14
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
HTML report on live meteor package testing is empty #23
Comments
@serut The Do you know if there is some hook/way to execute code right after mocha test runner has finished testing? Maybe you've seen something in this package or |
I don't think so, I think that mocha has hooks like afterTestsDone but I didn't look at it. If you want to check the client coverage, my favorite way would be with |
Thank you very much for your insights, @serut. I thought about mocha hooks too (the hook you refer is I already saw that code. spacejam works well, but what I'm trying to achieve is doing the coverage analysis on each meteor live reloading. When you execute What takes more time to execute spacejam is spawning meteor each time and compiling the code, but with the live reload, that gets faster. That's why I want to update the contents of the output folder after each live reload (which executes your package tests). This feature could be called live coverage 😄, and I think it would be very handy get live testing results and live coverage. I'll dig into Thanks anyway!! |
I'm closing this because of #30. After checking the new |
Expected Behavior
I expect to see the same HTML coverage report when I run
spacejam-mocha --coverage \"out_coverage\" ./
(manually navigating to.coverage/index.html
)Current Behavior
The HTML report shown when navigating to
localhost:3000/coverage
while commandCOVERAGE=1 meteor test-packages ./ --driver-package practicalmeteor:mocha
is empty:Possible Solution
No idea.
Steps to Reproduce (for bugs)
COVERAGE=1 meteor test-packages ./ --driver-package practicalmeteor:mocha
.localhost:3000/coverage
.IMPORTANT: you must have properly configured the meteor packages
lmieulet:meteor-coverage
andpracticalmeteor:mocha
in the filepackage.js
(sectionPackage.onTest()
) of your package.Context
I wanted to check the package coverage while writing my tests and seeing my tests results.
Your Environment
The text was updated successfully, but these errors were encountered: