Skip to content
This repository was archived by the owner on Oct 20, 2021. It is now read-only.

"Test mode" throws an AssertionError #171

Open
wagnermaciel opened this issue May 17, 2018 · 5 comments
Open

"Test mode" throws an AssertionError #171

wagnermaciel opened this issue May 17, 2018 · 5 comments

Comments

@wagnermaciel
Copy link

Hi,

In part 11 of the Blaze simple-todos tutorial I am getting this error

W20180517-18:34:00.829(-4)? (STDERR) "[object Object]" reporter blew up with error:
W20180517-18:34:00.852(-4)? (STDERR) AssertionError [ERR_ASSERTION]: path must be a string

with this error message

Exception while invoking method 'mocha/runServerTests' Error: invalid reporter "[object Object]"
when attempting to run in "test mode" with

meteor test --driver-package practicalmeteor:mocha

@cur33
Copy link
Contributor

cur33 commented Jun 7, 2018

I had the same problem which I fixed by removing practicalmeteor:mocha (i.e. meteor remove practicalmeteor:mocha and then by adding this fork instead, with the command meteor add cultofcoders:mocha. This worked for me. You could also do meteor add meteortesting:mocha, but that gave me some errors, so I went back to the cultofcoders package.

@alewitt
Copy link

alewitt commented Jun 12, 2018

im seeing same issue: Meteor 1.7.0.1

@cur33
Copy link
Contributor

cur33 commented Jun 13, 2018

@alewitt did you attempt my solution?

@alewitt
Copy link

alewitt commented Jun 13, 2018

No. I was just following the tutorial. Its not pressing that i have tests working right now, so i just figured i give it some time to get worked out.

MichaelJCole pushed a commit to MichaelJCole/tutorials that referenced this issue Nov 24, 2018
@tromgy
Copy link

tromgy commented Jan 30, 2019

switching to cultofcoders:mocha allows tests to run, but the only tests that run are in the tests/main.js, not the ones described in the tutorial (imports/api/tasks.tests.js)

It doesn't seem to pick up those at all. I even tried to put syntax errors in that file, and there were no error reports. The testing framework seems to ignore it completely.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants