karma: Karma is not able to run test cases on phantomJS

Hey, all the people here: you are doing this so wrong!

The point is to test your app with Karma in real browsers, the one that your users use… unless you want your tests to have no value at all.

I solved this issue by reinstalling node_modules

karma 
karma-chrome-launcher
karma-jasmine
karma-ng-html2js-preprocessor
karma-phantomjs-launcher
phantomjs

@antonyh sounds awfully irrational though, sounds like Microsoft 😦 good software shouldn’t magically fix itself upon restart or reinstall.

How to configure karma_start.js to disable web security and local to remote url access using phantom launcher?

I solved this issue by deleting the node_modules folder and running npm install again - PhantomJS and Karma ran flawlessly following this cleanup.

PhantomJS 2.1.1 on Linux Karma 1.2.0 Grunt 0.4.5

This issue accumulated a lot of different problems and is not actionable now. It has not been active for 2.5 years and PhantomJS has been archived two years ago. If you still experience issues with PhantomJS consider migrating to Chrome Headless or Firefox Headless.

If someone facing this problem in angular/cli, I’ve fixed this problem by uncommenting this lines in polyfill.ts: import ‘core-js/es6/symbol’; import ‘core-js/es6/object’; import ‘core-js/es6/function’; import ‘core-js/es6/parse-int’; import ‘core-js/es6/parse-float’; import ‘core-js/es6/number’; import ‘core-js/es6/math’; import ‘core-js/es6/string’; import ‘core-js/es6/date’; import ‘core-js/es6/array’; import ‘core-js/es6/regexp’; import ‘core-js/es6/map’; import ‘core-js/es6/weak-map’; import ‘core-js/es6/set’;

Hello everyone, I ran into this same (frustrating) issue and discovered the problem was in the karma config. Since I was using gulp to run karma / PhantomJS. When I changed singleRun: false -> true it started working for me again:

var gulp = require('gulp');
var Server = require('karma').Server;

// Run test once and exit
gulp.task('test', function (done) {
    new Server({
        configFile: __dirname + '/karma.conf.js',
        singleRun: true
    }, done).start();
});

You can also change this parameter directly inside of the karma config as well:

// Continuous Integration mode if true, Karma captures browsers, runs the tests and exits
singleRun: true,

The issue got resolved for me in Ubuntu 14.04 by deleting the node_modules directory from the project (which had been checked-in by someone else using a Macbook). I ran npm install again and the node_modules directory was recreated. We have also added the ‘node_modules’ directory to .gitignore

@pawelszymanski PhantomJS is great for unit testing javascript that is unlikely to behave differently between browsers. AngularJS controllers using Karma, for instance. For heavy DOM manipulation where different browsers may have varying behavior, PhantomJS isn’t a good fit. There is a use case for it, you’re just not seeing it. It’s ironic that you’re criticizing people for “doing it wrong” when you’re posting your personal opinions about a testing tool in a bug tracker. Talk about doing it wrong…

@pawelszymanski PhantomJS is is WebKit, and is just as much a browser as Safari and Chrome for the purposes of testing. The value is that it can be run headless on a server for automated testing. It isn’t necessarily the only form of testing that should be performed, but is helpful for catching regressions. The tests have plenty of value. Your comment on the other hand…