CODEWITHSUNDEEP
reactjsjestjsgitlab-cie2e-testing
vpv
vpv

Reputation: 938

How to run React Jest e2e tests in GitLab CI-CD pipeline?

Scenario:

I have configured e2e tests using Jest for a React web app. To run e2e tests locally, I had to start the server locally from a terminal window using npm start command and from another terminal window, execute the test command npm run test:e2e. I have both Chrome and Firefox browsers installed in my pc as a result e2e tests are running properly in local.

Now, I want to run these e2e tests as part of GitLab CI-CD pipeline and having issue with the following:

  1. How to ensure that browsers (Chrome/Firefox) are available to the GitLab runner? I got some tutorials which suggested to install required browser(s) as part of the pipeline step. Is it the best approach?

  2. Is it possible to achieve the same without installing the browser(s)? For example: using selenium_standalone-chrome images? If yes, how to do it?

Any reference to example link/code is highly appreciated. Thanks.

Upvotes: 1

Views: 2016

Answers (1)

vpv
vpv

Reputation: 938

In GitLab CI-CD pipeline (for Chrome browser only at the moment): 

E2Etest:
  stage: e2e
  image: node:10.15.3
  variables:
    CI_DEBUG_TRACE: "true"
  allow_failure: false
  script:
    - set -e
    - npm install


    - wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
    - sh -c 'echo deb http://dl.google.com/linux/chrome/deb/ stable main > /etc/apt/sources.list.d/google.list'
    - apt-get update
    - apt-get install -y xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic xvfb x11-apps imagemagick google-chrome-stable


    - npm run test:e2e:chrome
    - pkill node
  artifacts:
    paths:
      - coverage
    expire_in: 1 hr

Upvotes: 1

Related Questions