-
Notifications
You must be signed in to change notification settings - Fork 4.7k
How about using PhantomJS instead of Chrome? #53
Comments
What's the problem with using Chrome in your setup? If it's available, Karma should be able to use it. PhantomJS is not a browser. It is not compatible with Firefox or Chrome. Your users do not use phantomjs to run your app. So it makes no sense to run tests in PhantomJS. Also debugging test failures in PhantomJS is a PITA. |
We should really just address the issue of using chrome or other modern browser in your environment. Karma can launch Chrome on windows, so I don't quite understand what's the problem. |
Sorry to have created an issue of no real consequence. After a little fiddling to resolve the ENOENT error in Windows (also, I should have just RTFM), Karma works great from The issue with using Chrome is, I realized, myself. There is a guide to run Chrome with xvfb, but I could not replicate the results. I just got varying errors with issue I tried to fix (yesterday it was missing fonts today it is something else) and keep getting output like:
I don't know if this is just permissions but trying to run as root failed because Chrome would 'refuse' to do so... |
I develop on Windows and test on a Vagrant virtual machine. I tried installing Chrome with xvfb but ran into various issues (at least one seemingly intractable).
I suggest it would be very flexible for everyone (people with just a console available, as well as those that have a full GUI) if Karma was configured to use PhantomJS by default instead, as it is super comfortable to use in the command line, and quite trivial to install.
The text was updated successfully, but these errors were encountered: