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
action or some other means.
- 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/...
the browser to use
the report format to use
additionnal flags for the report generation
a boolean, false by default
configuration file path
An ‘execute’ action for use by generators.
execute actions have a mandatory
- uses: cypress/execute@v1 with: test: cypressProject/cypress/test.spec.js
the datasource to use
A ‘params’ action for use by generators.
params actions have mandatory
- 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 (
data can have two keys:
globalfor defining global parameters
testfor defining test parameters
the data to use for the automated test
the format to use for the automated test data