Angular 2 cli run tests on bitbucket pipelines

Question

I'm trying to run tests over bitbucket platform with the following configuration:

image: node:6.8.0

pipelines:
  default:
    - step:
        script:
          - echo 'deb http://dl.google.com/linux/chrome/deb/ stable main' > /etc/apt/sources.list.d/chrome.list
          - wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
          - set -x && apt-get update && apt-get install -y xvfb google-chrome-stable
          - ln -sf /usr/bin/xvfb-chrome /usr/bin/google-chrome
          - npm --version
          - npm install
          - npm test

And that's the output:

> ng test

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
13 10 2016 15:26:57.937:WARN [karma]: No captured browser, open http://localhost:9876/

WARNING in ./~/@angular/core/src/linker/system_js_ng_module_factory_loader.js
45:15 Critical dependency: the request of a dependency is an expression

WARNING in ./~/@angular/core/src/linker/system_js_ng_module_factory_loader.js
57:15 Critical dependency: the request of a dependency is an expression
13 10 2016 15:26:57.945:INFO [karma]: Karma v1.2.0 server started at http://localhost:9876/
13 10 2016 15:26:57.946:INFO [launcher]: Launching browser Chrome with unlimited concurrency
13 10 2016 15:26:58.033:INFO [launcher]: Starting browser Chrome
13 10 2016 15:26:58.421:ERROR [launcher]: Cannot start Chrome

13 10 2016 15:26:58.532:INFO [launcher]: Trying to start Chrome again (1/2).
13 10 2016 15:26:58.813:ERROR [launcher]: Cannot start Chrome

13 10 2016 15:26:58.814:INFO [launcher]: Trying to start Chrome again (2/2).
13 10 2016 15:26:59.049:ERROR [launcher]: Cannot start Chrome

13 10 2016 15:26:59.050:ERROR [launcher]: Chrome failed 2 times (cannot start). Giving up.

The problem is that karma is not able to start chrome browser. I think the problem happens with any docker enviroment. How can I run tests in bitbucket pipelines?

No, use angular cli default configuration of karma and proactor. Is there any posibility to use chrome, or I have to use phantom? — Serginho
– Serginho, Commented Oct 19, 2016 at 8:45
Do you particularly want to use a non-headless browser? Chrome is the default for Angular CLI projects, but switching to Phantom is trivial (see e.g. my project github.com/textbook/known-for-web). Alternatively, have you looked into something like Sauce Labs or installation e.g. Xvfb? This doesn't seem unique to bitbucket pipelines, I'd suggest some broader research. — jonrsharpe
– jonrsharpe, Commented Oct 19, 2016 at 8:54
@jonrsharpe I can use phantom, but I saw in any site that travisCI has chromium installed and users use it to execute tests. Even if you go to angular-cli project, you will see in their travis.yml that tests are run over chromium. Back to your answer, your tests are working properly with these config? — Serginho
– Serginho, Commented Oct 19, 2016 at 11:19
what problem are you actually trying to solve? Do you just want to get the tests running, or get them running in Chrome. Yes, my tests are working, but in TravisCI not a bitbucket pipeline. — jonrsharpe
– jonrsharpe, Commented Oct 19, 2016 at 11:20

Morgan O'Neal · Accepted Answer · 2016-10-28 17:37:29Z

Try switching your tests over to PhantomJS.

Install PhantomJS Runner https://github.com/karma-runner/karma-phantomjs-launcher

$ npm install --save-dev karma-phantomjs-launcher

Edit your karma.conf.js to use PhantomJS

// /karma.conf.js
module.exports = function (config) {
  config.set({
    // ...
    plugins: [
      // ...
      require('karma-phantomjs-launcher'),
      // ...  
    ],
    // ...  
    // browsers: ['Chrome'],
    browsers: ['PhantomJS'],
    phantomjsLauncher: {
      // Have phantomjs exit if a ResourceError is encountered 
      // (useful if karma exits without killing phantom)
      exitOnResourceError: true // Could require proxy if tests access images without /base path
    },
    //...
  });
};

This should now run your tests in PhantomJS instead of Chrome.

The default test script also runs watch so you might want to modify your package.json test script to be "test": "ng test --watch=false". If you want to have watch run for local development just launch with ng test instead of npm test.

Meligy · Accepted Answer · 2016-10-19 10:19:36Z

0

Try relying on this image instead:

https://github.com/mark-adams/docker-chromium-xvfb

answered Oct 19, 2016 at 10:19

Meligy

36.7k11 gold badges90 silver badges114 bronze badges

4 Comments

Serginho Over a year ago

Test it, and fails

Serginho Over a year ago

Yes, cannot start chrome

Meligy Over a year ago

Might be a stupid question, but did you remove the lines that add Chrome? (since it comes in the image itself)

Serginho Over a year ago

Obviously, ya. when I put the markadams' image, I only use npm install; npm test --no-watch. Good try to catch me. xD

Collectives™ on Stack Overflow

Angular 2 cli run tests on bitbucket pipelines

2 Answers 2

Comments

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related