v1.11.0 add timeout parameter

See 09b3fbe

v1.10.0 feat: additional executors with Chrome 73-76

See #171 and https://github.com/cypress-io/circleci-orb/blob/master/docs/executors.md

feat: custom cache key for install job

Which helps in monorepo situations

version: 2.1
orbs:
  cypress: cypress-io/cypress@1
workflows:
  build:
    jobs:
      - cypress/install:
          cache-key: cache-{{ arch }}-{{ .Branch }}-{{ checksum "frontend/package.json" }}
      - cypress/run:
          yarn: true
          cache-key: cache-{{ arch }}-{{ .Branch }}-{{ checksum "frontend/package.json" }}
          working_directory: frontend

v1.8.0 Custom working directory

You can specify a custom working directory for commands. Useful in the situations where the front-end tests live in a subfolder.

• PR #144

version: 2.1
orbs:
  cypress: cypress-io/[email protected]
workflows:
  build:
    jobs:
      - cypress/run:
          working_directory: frontend

• added base-12-6-0 executor with Node 12.6.0

v1.7.0 add no-workspace parameter for faster single "cypress/run" job

Faster "cypress/run" job that does not attach workspace,
because there are no jobs that follow, so no need to save anything.

version: 2.1
orbs:
  cypress: cypress-io/cypress@1
workflows:
  build:
    jobs:
      - cypress/run:
          no-workspace: true

v1.6.0 pass custom NPM cache key

From PR #107 which adds new parameter cache-key, that will make possible

• Use yarn.lock as cache checksum
• Properly share cache between steps

Closes #106

v1.5.1: show good error message if package-lock.json is missing before "npm ci"

Example in https://circleci.com/gh/cypress-io/cypress-example-circleci-orb/87

closes #75

v1.5.0 feat: yarn install uses "--frozen-lockfile" flag

Better yarn installs on CI with yarn install --frozen-lockfile command

v1.4.0 feat: support yarn install command

If your project already uses yarn, you can use yarn install on CircleCI to install dependencies.

version: 2.1
orbs:
  cypress: cypress-io/[email protected]
workflows:
  build:
    jobs:
      - cypress/run:
          yarn: true

Example: https://github.com/bahmutov/cypress-yarn-circle-example

Note, that when using yarn: true only folder ~/.cache will be cached. Since it already contains Cypress binary, everything should just work.

v1.3.0: feat: cache dependencies per architecture

With this change you can run Circle builds on multiple architectures in parallel without bringing wrong dependencies. For example you can run tests on Linux and on Mac like this:

version: 2.1
orbs:
  cypress: cypress-io/[email protected]
executors:
  mac:
    macos:
      xcode: 10.1.0
workflows:
  build:
    jobs:
      - cypress/run:
          name: Linux test
      - cypress/run:
          name: Mac test
          executor: mac

Note: if you use cypress/install followed by cypress/run and want to do it both on Mac and Linux (or several combinations of different Docker images), you need to separate workflows - otherwise workspace files from one architecture will overwrite workspace files from another architecture. Do something like this:

workflows:
  mac-build:
    jobs:
      - cypress/install:
           executor: mac
      - cypress/run:
          executor: mac
          requires:
          - cypress/install
  linux-build:
    jobs:
      - cypress/install
      - cypress/run:
          requires:
          - cypress/install