Add support for headless Chrome/ChromeCanary #111

dpogue · 2017-03-21T04:15:11Z

Tested on Linux with google-chrome-unstable, but as of today it should be support in macOS Chrome Canary as well.

Not really expecting this to be merged until headless support hits a stable release across multiple OSes, but figured I'd open a PR for anyone trying to figure out how to get it working. I was thinking of publishing it to npm as karma-headless-chrome-launcher, but it seems that name is already in use.

dignifiedquire · 2017-03-21T14:49:56Z

Thank you, I'm generally not opposed to merge this, but I would like some docs saying that it is experimental and where to look for details about it.

dignifiedquire · 2017-03-21T14:50:23Z

It would also be great if we could add it to travis and test it there if that's possible

vvo · 2017-04-13T14:58:23Z

test/jsflags.spec.js

+    expect(headlessGetOptions.call(context, url, args, parent)).to.be.eql([
+      '-incognito',
+      '--headless',
+      '--disable-gpu',


Curiosity: What are the pros of using incognito and disable-gpu?

--disable-gpu is currently needed with headless because of linking errors with osmesa.so. That will hopefully not be required once Chrome switches to their SwiftShader library as a software rendering engine. See https://bugs.chromium.org/p/chromium/issues/detail?id=617551 for details.

-incognito is just an example flag in the test, ensuring that it gets passed through.

agaripian · 2017-04-18T04:06:37Z

@dpogue thanks for this PR! I am using your repo/branch for karma-chrome-launcher but I am getting the following Error inside my docker container. Any Ideas what might be causing the
EACCES error? Its using ubuntu:16.04 I also started the container with --cap-add=SYS_ADMIN

18 04 2017 03:49:43.520:INFO [launcher]: Starting browser ChromeCanaryHeadless
18 04 2017 03:49:43.538:ERROR [karma]: { Error: spawn EACCES
    at exports._errnoException (util.js:1018:11)
    at ChildProcess.spawn (internal/child_process.js:319:11)
    at exports.spawn (child_process.js:378:9)
    at spawnWithoutOutput (/app/node_modules/karma/lib/launchers/process.js:145:24)
    at Object.ProcessLauncher._execCommand (/app/node_modules/karma/lib/launchers/process.js:63:21)
    at Object.ProcessLauncher._start (/app/node_modules/karma/lib/launchers/process.js:28:10)
    at Object.<anonymous> (/app/node_modules/karma/lib/launchers/process.js:14:10)
    at emitOne (events.js:101:20)
    at Object.emit (events.js:188:7)
    at Object.BaseLauncher.start (/app/node_modules/karma/lib/launchers/base.js:42:10)
    at Object.j (/app/node_modules/karma/lib/launcher.js:116:17)
    at Object.setTimeout.bind.j (/app/node_modules/qjobs/qjobs.js:143:18)
    at ontimeout (timers.js:380:14)
    at tryOnTimeout (timers.js:244:5)
    at Timer.listOnTimeout (timers.js:214:5)
 code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }

npm ERR! Linux 4.4.17-boot2docker
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "karma"
npm ERR! node v6.10.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! be.net@0.0.0 karma: `karma start --single-run --verbose`
npm ERR! Exit status 1

dpogue · 2017-04-18T04:13:17Z

That sort of error seems to be common if you ran the npm install with sudo and are trying to run the karma command without sudo. Maybe try a chown/chmod on your node_modules folder?

agaripian · 2017-04-18T04:18:18Z

I figured it out.. It was related to my env variable that I had set, Once I removed it it worked fine. process.env.CHROME_CANARY_BIN = '/opt/google/chrome-unstable'; <- that caused the issue.

unseen1980 · 2017-04-21T13:09:57Z

I can confirm that in my case it worked without issues. I used it for unit testing. Great work, thanks @dpogue 👍

mgol · 2017-04-24T07:29:00Z

index.js

+  name: 'ChromeHeadless',
+
+  DEFAULT_CMD: {
+    // Try chromium-browser before chromium to avoid conflict with the legacy


This comment is out of date, isn't it?

hmm, yes it is (although it is also out-of-date further up in the file where I copied this block from)

klaussilveira · 2017-04-25T21:00:30Z

My simpler Jenkins setup likes this. 👍

dpogue · 2017-05-01T17:28:03Z

For those who are wanting to use this before it's merged, you can tell npm to install it from the git branch:
npm install --save-dev dpogue/karma-headless-chrome-launcher

Headless Chrome is supported in Chrome 59 on Linux and Mac. Windows is not supported yet (they're aiming for Chrome 60). See https://developers.google.com/web/updates/2017/04/headless-chrome for more info about headless chrome.

I have added tests to the PR, and will try to get some docs written.

rogeriopvl · 2017-05-01T20:43:45Z

@dignifiedquire I think we're good to merge this. Do you agree?

dignifiedquire · 2017-05-01T20:50:03Z

Thank you everyone 🎉

egoroof · 2017-05-02T09:04:35Z

Will it be a new release soon?

dignifiedquire · 2017-05-02T16:02:48Z

@rogeriopvl I can cut a new release, but maybe this should be fixed first #120?

rogeriopvl · 2017-05-02T17:06:58Z

@dignifiedquire #120 doesn't sound at all related with karma-chrome-launcher.

mgol · 2017-05-02T17:08:49Z

@dignifiedquire #120 is not a bug, it will fail like that for people trying this with current stable Chrome, i.e. v58 (and maybe even with v59 on Windows as there it will be officially supported only in v60 & newer).

dignifiedquire · 2017-05-02T17:12:30Z

Okay will do a release then

dignifiedquire · 2017-05-02T17:15:05Z

done 2.1.0

cmacdonnacha · 2017-12-08T14:54:10Z

Will this work with Bamboo CI? I changed my karma config from:

browsers: ['PhantomJS']

to

browsers: ['ChromeHeadless']

but it seems to be failing now.

Also, does this default to phantomjs if chrome headless fails?

See: karma-runner/karma-chrome-launcher#111 (comment).

Add support for headless Chrome/ChromeCanary

a98a479

rogeriopvl added the needs: feedback-from-author label Mar 28, 2017

Add a test for headlessGetOptions

982e485

intellix mentioned this pull request Apr 13, 2017

Targeting more than JSDOM jestjs/jest#848

Open

vvo reviewed Apr 13, 2017

View reviewed changes

rogeriopvl mentioned this pull request Apr 13, 2017

New Launcher - Chrome Headless karma-runner/karma#2489

Closed

pirelenito mentioned this pull request Apr 15, 2017

Use headless Chrome instead of PhantomJS to run tests 🤖 saguijs/sagui#337

Closed

Nighthawk14 mentioned this pull request Apr 17, 2017

Switch from PhantomJS to Headless Chrome Cognizant-CDE-Australia/generator-confit#124

Closed

mgol reviewed Apr 24, 2017

View reviewed changes

LukasReschke mentioned this pull request Apr 25, 2017

JS tests failing on CI nextcloud/server#4487

Closed

dignifiedquire merged commit 7446181 into karma-runner:master May 1, 2017

rogeriopvl removed the needs: feedback-from-author label May 1, 2017

mAAdhaTTah mentioned this pull request May 1, 2017

Switch to Headless Chrome mAAdhaTTah/brookjs#57

Closed

Trendy mentioned this pull request May 8, 2017

Add default support for headless Chrome travis-ci/travis-ci#7650

Closed

bendrucker mentioned this pull request May 11, 2017

Switch from PhantomJS to Chrome launcher nikku/karma-browserify#208

Closed

priley86 mentioned this pull request May 16, 2017

upgrade web components of patternfly to custom elements v1 patternfly-webcomponents/patternfly-webcomponents#40

Merged

frandiox mentioned this pull request May 25, 2017

Headless Chrome for unit tests vuejs-templates/webpack#726

Closed

kibertoad mentioned this pull request Jul 3, 2017

Added test execution on Chrome browser. Updated grunt, grunt plugins. Fixed new ESLint warning. melonjs/melonJS#890

Merged

joshlory pushed a commit to joshlory/karma that referenced this pull request Feb 27, 2018

Add "ChromeHeadless" to list of possible browsers

cfd2604

See: karma-runner/karma-chrome-launcher#111 (comment).

joshlory mentioned this pull request Feb 27, 2018

Documentation update: add "ChromeHeadless" to list of possible browsers karma-runner/karma#2940

Merged

dignifiedquire pushed a commit to karma-runner/karma that referenced this pull request Mar 3, 2018

docs: add "ChromeHeadless" to list of possible browsers

e7b9ab8

See: karma-runner/karma-chrome-launcher#111 (comment).

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add support for headless Chrome/ChromeCanary #111

Add support for headless Chrome/ChromeCanary #111

dpogue commented Mar 21, 2017

dignifiedquire commented Mar 21, 2017

dignifiedquire commented Mar 21, 2017

vvo Apr 13, 2017

dpogue Apr 13, 2017

agaripian commented Apr 18, 2017

dpogue commented Apr 18, 2017

agaripian commented Apr 18, 2017

unseen1980 commented Apr 21, 2017

mgol Apr 24, 2017

dpogue May 1, 2017

klaussilveira commented Apr 25, 2017

dpogue commented May 1, 2017

rogeriopvl commented May 1, 2017

dignifiedquire commented May 1, 2017

egoroof commented May 2, 2017

dignifiedquire commented May 2, 2017

rogeriopvl commented May 2, 2017

mgol commented May 2, 2017

dignifiedquire commented May 2, 2017

dignifiedquire commented May 2, 2017

cmacdonnacha commented Dec 8, 2017 •

edited

Loading

Add support for headless Chrome/ChromeCanary #111

Add support for headless Chrome/ChromeCanary #111

Conversation

dpogue commented Mar 21, 2017

dignifiedquire commented Mar 21, 2017

dignifiedquire commented Mar 21, 2017

vvo Apr 13, 2017

Choose a reason for hiding this comment

dpogue Apr 13, 2017

Choose a reason for hiding this comment

agaripian commented Apr 18, 2017

dpogue commented Apr 18, 2017

agaripian commented Apr 18, 2017

unseen1980 commented Apr 21, 2017

mgol Apr 24, 2017

Choose a reason for hiding this comment

dpogue May 1, 2017

Choose a reason for hiding this comment

klaussilveira commented Apr 25, 2017

dpogue commented May 1, 2017

rogeriopvl commented May 1, 2017

dignifiedquire commented May 1, 2017

egoroof commented May 2, 2017

dignifiedquire commented May 2, 2017

rogeriopvl commented May 2, 2017

mgol commented May 2, 2017

dignifiedquire commented May 2, 2017

dignifiedquire commented May 2, 2017

cmacdonnacha commented Dec 8, 2017 • edited Loading

cmacdonnacha commented Dec 8, 2017 •

edited

Loading