-
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
There is no route for the path: /local #16
Comments
Hello @rws-github .
This repository uses that system: https://github.com/serut/meteor-coverage-app-exemple and it works great |
It now runs the tests. I don't see any coverage being output.
.coverage.json has Nothing in .coverage after run |
I don't have any log to help you. Does the |
Can you retry with the lastest release please ? |
I just noticed my version of meteor-coverage is set to 0.8.1 and I get this on update:
|
Sorry, wrong command. This installed: meteor add 'lmieulet:meteor-coverage@=1.0.1' |
And this is working ? Do you see yours files ? |
It seems to just start the app normally and not run tests:
|
You need to replace mocha to mocha-console-runner |
It did the same thing. If I run: It prints that it is covering things but I get no output of coverage at the end. |
Yeap, you require spacejam to export coverage reports.
By the way, It can be run with
It means:
If you want to start your app and do everything by yourself
The readme of the package have been rewritten with everything I'm saying, it will help you a lot, and if not use the meteor-coverage-app-exemple to see how things works. |
It worked when I ran: COVERAGE=1 COVERAGE_APP_FOLDER=$(pwd)/ spacejam test --driver-package practicalmeteor:mocha-console-runner --coverage out_coverage Thanks for your help and project! |
You welcome ! 🍻 |
Existing tests that run in
meteor test --once --driver-package dispatch:mocha-phantomjs
do not run with
spacejam test --driver-package practicalmeteor:mocha-console-runner --coverage out_coverage
Expected Behavior
Existing tests to run
Current Behavior
Ouput indicates its testing a path of /local for no apparent reason:
The text was updated successfully, but these errors were encountered: