You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 28, 2023. It is now read-only.
Hello! I was trying to put together a PR for fix the fact that the adapter doesn't follow the mocha reporter spec, but I can't get the tests for the repo to run, which is annoying :(
Does anyone know what I'm doing wrong or has the repro just have bitrot. That said the test:lib pure mocha script works fine. It also appears mock-fs dependency is so out of date it doesn't support node 8 as well...
>$ npm install
>$ npm test
> [email protected] test /Users/XXXXX/Code/Karama/karma-mocha
> grunt test
Running "karma:adapter" (karma) task
13 10 2017 22:05:59.370:WARN [watcher]: Pattern "/Users/XXXXX/Code/Karama/karma-mocha/lib/adapter.js" does not match any file.
13 10 2017 22:05:59.399:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/
13 10 2017 22:05:59.399:INFO [launcher]: Launching browser Chrome with unlimited concurrency
13 10 2017 22:05:59.405:INFO [launcher]: Starting browser Chrome
13 10 2017 22:06:00.019:INFO [Chrome 61.0.3163 (Mac OS X 10.12.6)]: Connected on socket 5xqb-Hn_15fRzgx8AAAA with id 87474646
Chrome 61.0.3163 (Mac OS X 10.12.6) ERROR
Uncaught ReferenceError: describe is not defined
at test/src/adapter.spec.js:23
Chrome 61.0.3163 (Mac OS X 10.12.6): Executed 0 of 0 ERROR (0.147 secs / 0 secs)
Warning: Task "karma:adapter" failed. Use --force to continue.
Aborted due to warnings.
npm ERR! Test failed. See above for more details.
Hello! I was trying to put together a PR for fix the fact that the adapter doesn't follow the mocha reporter spec, but I can't get the tests for the repo to run, which is annoying :(
Does anyone know what I'm doing wrong or has the repro just have bitrot. That said the test:lib pure mocha script works fine. It also appears mock-fs dependency is so out of date it doesn't support node 8 as well...
@dignifiedquire @maksimr
The text was updated successfully, but these errors were encountered: