DamonOehlman / travis-multirunner

A simple configuration for running (limited) multibrowser tests on travis ci
8 stars 14 forks source link

A little helper for karma users #17

Open thepatrick opened 8 years ago

thepatrick commented 8 years ago

After having trouble setting up a new project wit travis-multirunner today, it'd be great if it set ${BROWSER}_BIN - karma-chrome-launcher and karma-firefox-launcher both support this as an explicit way to tell it which one to use

fippo commented 7 years ago

@thepatrick i'm looking in karma stuff right now -- this would be done in the global env section?

env:
  global:
    - DISPLAY=:99.0
    - FIREFOX_BIN=path-to-start-firefox.sh
    - CHROME_BIN=path-to-start-chrome.sh

(I miss the "why do these guys work on a sunday???" moments :-))

fippo commented 7 years ago

ah... that did not work out. Must be set to

CHROME_BIN=browsers/bin/chrome-$BVER
silviapfeiffer commented 7 years ago

I'm having fun on a Sunday also, but more around spec writing: https://github.com/w3c/webvtt/pull/349 ;-)

fippo commented 7 years ago

heh. But it is winter down there :-)

TIL: the matrix variables are evaluated after the global ones so we can't define CHROME_BIN in the "global" section... see https://travis-ci.org/webrtc/adapter/jobs/246782477#L527