Jeff Lowery

In addition to input types, have mutator types? The idea is that if a mutator type is returned from a mutation requests, it is treated as an extension of the...

My tests have been failing to generate reports since Dec. 11. Not sure of the cause. Node 6.11.2. Using: SERVER_UNDER_TEST="$1" mocha ./tests --recursive --slow 1500 --reporter mochawesome

I can verify that when an assert is fired, I get no report. If all tests pass, then a report is generated. More details in a moment.

Here we go; the second test fails and no report is generated. This is on a Mac, Sierra OS **mocha ./tests/bugTest --slow 1500 --reporter mochawesome** bugTest.js ``` var chai =...

Could be some bug triggered by one of the global module versions. Here's mine: npm ls -g -depth=0 /usr/local/lib ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├──...

I cloned your repo and the good news is: _it doesn't work_. I think that's good news: it eliminates it being a project issue. ```mocha test.js --reporter mochawesome Bug test...

Switched over to my Windows 10 box and running into different issues. I don't think I've tried running mocha on a PC before. If I just do an **npm install**...

Okay, I played around with this a bit more on my PC. --save-dev mocha doesn't work (mocha not recognized), but --save mocha does. Now the test runs, mochawesome works, but...

And after playing around with NODE_ENV in powershell, I can't get mochawesome to fail, no matter if I install mocha with **--save** or **--save-dev**, with **NODE_ENV=production** or **=development**.

Now I am unable to reproduce this (using the test project) on my Mac. I am hoping the debug log provided some useful info.