Open logankoester opened 9 years ago
As a workaround, you can install phantomjs-1.x
alongside phantomjs-2.x
(on Arch Linux, the phantomjs-1.8 AUR package exists for this purpose) somewhere on your system and then set the PHANTOMJS_EXECUTABLE
environment variable to point to it.
PhantomJS 2.0 removes CoffeeScript support (https://github.com/ariya/phantomjs/issues/12410), which causes CasperJS to hang until killed on
.coffee
files, resulting in an ENOENT error inmeteor-casperjs
on the xml report files that never get created.We could remove coffee support from
meteor-casperjs
to match, but I'd strongly prefer not to.The solution would be to compile the coffee files to a temporary location in
runTestFile()
prior to running the tests.HOWEVER CasperJS is already aware of this issue (https://github.com/n1k0/casperjs/issues/1203), and they are currently considering adding that compile step themselves.
If we're feeling patient, we can wait and see where https://github.com/n1k0/casperjs/issues/1203 goes on their end.