Closed OctoD closed 9 years ago
Neat.... thanks for the report, will look into this probably this weekend at some point.
This looks like a problem with your test script -- do you get the same thing running mocha
without using mocha-runner ?
I'm sorry but the test works normally when launched by the command line.
Ok, so there's a few problems going on.
vm
module.require
declaration in mocha.opts isn't coming through, so each of the tests is failing because it can't find should. I'm not entirely sure why this is -- it requires a bit more investigation on my part to figure out (digging through mocha code)I've fixed the first two and pushed up as 1.1.0 -- (in all honesty, screwed up the apm command, intended that to be 1.0.3) -- anyway, I'll need to think how to fix the others.
I was able to fix the doosy -- actually not as hard as I originally thought. I was able to create a fork to a worker js file that did the actual running. Of course it has zero atom context so say goodbye to potentially running package specs with this runner -- but it does clean itself up nicely now.
Latest version is 1.1.1 -- last thing I need to do is figure out why things required through mocha.opts aren't coming through.
I've fixed up the rest of the problems and am now able to run the ride-css tests successfully.
Closing this now -- thanks for reporting!
Great! Thanks for the help and the nice work!
Atom Version: 1.0.0 System: Ubuntu 15.04 Thrown From: mocha-runner package, v1.0.2
Stack Trace
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'".
Commands
Config
Installed Packages