Skip to content

Latest commit

 

History

History

factory

README.md

cypress/factory

cypress/factory is a Docker image that can be used with ARG instructions in a custom-built Dockerfile to generate a new Docker image with specific versions of:

  • Node.js
  • Yarn v1 Classic
  • Chrome
  • Firefox
  • Edge
  • Cypress

Tags

cypress/factory images on Cypress on Docker Hub use image tags in the form:

  • <factory version>
  • latest

for example:

  • cypress/factory:4.0.2
  • cypress/factory:latest

To avoid unplanned breaking changes, specify a fixed <factory version> tag, not the latest tag. The latest tag is linked to the latest released cypress/factory image and is updated without notice.

Benefits

  • Freedom to choose which versions to test against.
  • No need to wait on an official release to test the latest version of a browser.
  • Smaller Docker image sizes especially when not including unused browsers.
  • Easily test multiple browser versions.
  • Reduced maintenance and pull requests in this repo.
  • Ability for Cypress to offer more variations of Docker images at low cost.

API

The following ARG variable values can be set to define what versions the Docker image includes in its build.

If no ARG variables are defined, only the default version of Node.js will be installed. This can still be a useful container though since we will also install any dependencies required to run Cypress.

NODE_VERSION

The version of Node.js to install in the Docker image. The exact version must be used, no wildcards or shorthands are supported. If the ARG variable is not defined or an empty string, the default version of Node.js (defined in .env as FACTORY_DEFAULT_NODE_VERSION) is installed. Node.js is a prerequisite for Cypress.

Example: NODE_VERSION='20.14.0'

Node Versions

YARN_VERSION

The version of Yarn v1 Classic to install (via npm). If the ARG variable is unset or an empty string, Yarn is not installed.

Example: YARN_VERSION='1.22.22'

Yarn versions

CYPRESS_VERSION

The version of Cypress to install (via npm). If the ARG variable is unset or an empty string, Cypress is not installed.

Example: CYPRESS_VERSION='13.11.0'

Cypress versions

CHROME_VERSION

The version of Chrome to install. If the ARG variable is unset or an empty string, Chrome is not installed. The exact version must be used, no wildcards or shorthands are supported.

Example: CHROME_VERSION='125.0.6422.141-1'

Chrome versions

FIREFOX_VERSION

The version of Firefox to install. If the ARG variable is unset or an empty string, Firefox is not installed. The exact version must be used, no wildcards or shorthands are supported.

Example: FIREFOX_VERSION='126.0.1'

Firefox versions

EDGE_VERSION

The version of Edge to install. If the ARG variable is unset or an empty string, Edge is not installed. The exact version must be used, no wildcards or shorthands are supported.

Example: EDGE_VERSION='125.0.2535.85-1'

Edge versions

Usage

The Docker cypress/factory build process works by relying on the ONBUILD Docker instruction to run commands at the image's build time. To make use of the Docker cypress/factory image and process, users will have to create a Dockerfile to declare what dependency versions are desired. Docker ARG variables can be specified in a number of ways, some of which are demonstrated below. For each of these examples we are building the equivalent of the cypress/browsers Docker image with Cypress additionally installed. In each instance, since the example is only testing the Chrome version, the examples could just install Chrome by itself if the other browsers were not used.

In the examples below, we install Cypress into the Docker image using:

RUN npm install cypress --save-dev
RUN npx cypress install

The additional npx cypress install command ensures that the Cypress binary component is installed, even if the Docker build step is re-run. The Docker build cache process may otherwise incorrectly optimize the build and fail to include the Cypress binary in the image, leading to run failures.

Example project

To test the following Docker build examples you need to have a Cypress project available. You can create a simple Cypress E2E project by following these steps:

mkdir cy-example-test # or another directory of your choice
cd cy-example-test
npm init -y
npm install cypress --save-dev
npx cypress open

In the Cypress GUI then:

  • Select "E2E Testing"
  • Select "Continue"
  • Select "Electron" browser
  • Select "Create new spec"
  • Select "Create spec"
  • Close all Cypress windows

Finally, test that the spec cypress/e2e/spec.cy.js runs:

npx cypress run

In the Dockerfile

ARG variables can be defined directly in the Dockerfile to make the variables available when the container is built.

Create a Dockerfile with the following content:

# Args are defined in the Dockerfile before the FROM command.
# Using these args will cause an image to be created with
# Node.js (default version from .env file), Chrome, Firefox and Edge.
ARG CHROME_VERSION='125.0.6422.141-1'
ARG EDGE_VERSION='125.0.2535.85-1'
ARG FIREFOX_VERSION='126.0.1'

FROM cypress/factory

COPY . /opt/app
WORKDIR /opt/app
RUN npm install cypress --save-dev
RUN npx cypress install

Then, in the same directory as the Dockerfile, run the following commands to build the Docker image and run Cypress against the Chrome browser.

docker build . -t test
docker run -it --rm test npx cypress run -b chrome

At build time

ARG variables can be passed to the docker build command with the --build-arg flag. Note: any value set via the command line will override the default ARG variable value provided in the Dockerfile.

Create a Dockerfile with the following content:

FROM cypress/factory

COPY . /opt/app
WORKDIR /opt/app
RUN npm install cypress --save-dev
RUN npx cypress install

Run the Docker commands:

docker build . --build-arg CHROME_VERSION='125.0.6422.141-1' --build-arg EDGE_VERSION='125.0.2535.85-1' --build-arg FIREFOX_VERSION='126.0.1' -t test
docker run -it --rm test npx cypress run -b chrome

In docker-compose.yml

Finally, Dockerfile ARG variable values can be specified in the docker-compose.yml file using compose args build arguments.

Create a docker-compose.yml file with the following content:

services:
  test:
    build:
      context: .
      args:
        CHROME_VERSION: '125.0.6422.141-1'
        EDGE_VERSION: '125.0.2535.85-1'
        FIREFOX_VERSION: '126.0.1'
    command: npx cypress run

and a Dockerfile with this content:

FROM cypress/factory

COPY . /opt/app
WORKDIR /opt/app
RUN npm install cypress --save-dev
RUN npx cypress install

Run the Docker commands:

docker compose build test
docker compose run --rm test

Reducing the size of the docker container

As mentioned above we can reduce the size of the Docker image by removing browsers we aren't using.

Since this example only uses Chrome, removing Edge and Firefox is as simple as not including a version.

Create a Dockerfile with the following content:

ARG CHROME_VERSION='125.0.6422.141-1'

FROM cypress/factory

COPY . /opt/app
WORKDIR /opt/app
RUN npm install cypress --save-dev
RUN npx cypress install

Then, in the same directory as the Dockerfile, run the following commands to build the Docker image and run Cypress against the Chrome browser.

docker build . -t test
docker run -it --rm test npx cypress run -b chrome

The released cypress/base image (no browsers) has a compressed size on Docker Hub of ~ 230 MB. The cypress/browsers image for linux/amd64 has a compressed image size of ~ 840 MB. By generating a custom image with unneeded browsers removed, the image size can be correspondingly reduced.

Version Testing

Due to the large amount of possible version combinations, we're not able to exhaustively test each combination of versions, nor do we block versions that are incompatible. For example, Cypress 12 removed support for Node.js version 12.0.0. You are still able to generate a container with node 12.0.0 and Cypress 12, but Cypress will fail to run. This is because the factory supports earlier versions of Cypress and must support earlier versions of node.

If you run across a combination that should reasonably work, but doesn't, log an issue and we will take a look at supporting it.

Additionally this docker image and containers generated from it are intended for test use only, and are not intended for hosting services in a production environment.