Skip to content

cypress

cypress/cypress@v1

Process ‘cypress’ action.

If the action is used more than once in a job, it is up to the caller to ensure no previous test execution results remains before executing a new test.

It is also up to the caller to attach the relevant reports so that publishers can do their job too, by using the actions/get-files@v1 action or some other means.

Example

- uses: cypress/cypress@v1
  with:
    browser: chrome
    reporter: junit
    reporter-options: "mochaFile=mocha_results/test-output-[hash].xml,toConsole=true"
    headless: true
    env: profile=postgres
    config-file: cypress/config/...

Inputs

  • browser (optional)

    the browser to use

  • reporter (optional)

    the report format to use

  • reporter-options (optional)

    additionnal flags for the report generation

  • headless (optional)

    a boolean, false by default

  • env (optional)

    additionnal properties

  • config-file (optional)

    configuration file path

cypress/execute@v1

An ‘execute’ action for use by generators.

execute actions have a mandatory test input.

Example

- uses: cypress/execute@v1
  with:
    test: cypressProject/cypress/test.spec.js

Inputs

  • test (required)

    the datasource to use

cypress/params@v1

A ‘params’ action for use by generators.

params actions have mandatory data and format inputs.

Example

- uses: cypress/params@v1
  with:
    data:
      global:
        key1: value1
        key2: value2
      test:
        key1: value3
        key3: value4
    format: format

format must so far be SQUASHTM_FORMAT (tm.squashtest.org/params@v1).

data can have two keys:

  • global for defining global parameters
  • test for defining test parameters

Inputs

  • data (required)

    the data to use for the automated test

  • format (required)

    the format to use for the automated test data