Missing options from cypress-io/github-action : start, wait-on, config-file, record and parallel

[adrienjoly]

Initial problem

On the CI (GitHub Actions) of our open-source project, we are sometimes getting a APPLITOOLS_API_KEY env variable is missing error when running our Cypress tests (example: https://github.com/openwhyd/openwhyd/actions/runs/3787192787/jobs/6439531260#step:8:6784), despite the fact that we do pass that env var to Cypress' github action. Cf https://github.com/openwhyd/openwhyd/blob/master/.github/workflows/ci.yml#L296.

Solution proposed by Applitools support

In response to this problem, Applitools support suggested that we use the colbyfayock/applitools-eyes-action action instead of Cypress', so we could pass APPLITOOLS_API_KEY more reliably.

Unfortunately, I fear that migrating over to that github action would prevent us from running our tests concurrently, because the parallel option is provided by cypress-io/github-action but not by colbyfayock/applitools-eyes-action. So, migrating it would result in a substantial increase of time needed to run our tests.

Question

What can we do to pass APPLITOOLS_API_KEY more reliably (to solve the initial problem) while still benefiting from the parallel option of cypress-io/github-action?

[adrienjoly]

Update / related note: Since we've upgraded Cypress 8.6 --> 12.2 and Eyes-cypress 3.23 --> 3.28 (cf openwhyd/openwhyd#589), we haven't witnessed any re-occurrence of "APPLITOOLS_API_KEY env variable is missing" error. So we may keep using cypress-io/github-action for now.