Nathan Black

You installed it locally and it's saying that? Yes, and since `mocha-casperjs` doesn't run in node it won't have the global path fallbacks so it has to have it globally....

> Would it be desirable/feasible to ensure that the isatty function returns false in this case? Yes, that makes sense.

This is a commander bug as it seems to always add a -h for help even though we define an option for it.

Yeah you should be using slimerjs `0.9.6` to ensure you include laurentj/slimerjs#78 otherwise the exit code will always be 0.

slimerjs exit codes were always 0 before that change, which landed in `0.9.6`. Make sure you are using exactly `0.9.6`. I do need to take another look at slimerjs now...

I can see that. One thing to note is that `mocha-phantomjs` can't know about what files you need to watch, but the same thing is true for browser sync that...

Phantomjs 1 didn't support this so `mocha-phantomjs` didn't support it explicitly. However if you use a before hook, you could use the API to set the cookies as you wish.

You can either pipe to a file with the shell `slimerjs .... > output.tap` or use the `--file` option. But are your tests hanging or `mocha-phantomjs-core`?

> I also now see that system.stderr.writeLine doesn't work on CMD or GIT bash... Because slimerjs doesn't support it. What version of slimerjs are you using? I had the tests...

`0.9.6` or `0.906.1` ? that's an odd build number....