Consider integrating the problems gulp-spawn-mocha had tried to solve

[phated]

The github project seems to have been removed, but from my email:

I was having problems with the cache, I don't have a link to anything it just seemed like a limitation of the way it was constructed. That try catch statement will get errors but you can still crash the process (e.g., and naively, process.exit(1). Furthermore, if any variables are set outside of modules (e.g., global scope) then those aren't cleared in the existing mocha plugin which I why I said that a new process will always start cleanly.

[dkushner]

I was also looking for some of the functionality offered by gulp-spawn-mocha, namely the inclusion of the ability to set environment variables like NODE_ENV. I can't say that I necessarily agree with starting a new process to run every test file. Is that in fact what mocha does normally? It certainly doesn't seem sane to me. If you are faffing about in GLOBAL then you better damn well expect that those properties will be available globally. That particular case seems more like bad practice than a problem with gulp-mocha.

[sindresorhus]

I give up. He was right. The Mocha programmatic API is just completely horrible and buggy. Going to spawn instead...

[shellscape]

@sindresorhus was your intention with the last comment you made that you were going to scrap using mocha as a straight require and instead spawn mocha in a cp?

[sindresorhus]

@shellscape Yes