• follows on from and replacesGithub actions: "Re-run failed jobs" will run the entire test suite #531

What would you like?

Scenario

A GitHub Actions workflow contains a job using theparallel option ofcypress-io/github-action recording toCypress Cloud which runs Cypress tests in multiple containers.

One or more Cypress tests fail.

GitHub Actions offers the optionRe-run failed jobs

Enhancement

GitHub Actions and Cypress Cloud should work together so that selectingRe-run failed jobs only re-runs failed jobs using a frozen set of load-balanced Cypress test specs, so that each failed job runs with the same test specs it used in its previous run. The Cypress tests which were distributed to other jobs, and which were previously successful, should not be re-run.

Why is this needed?

Reduce the overhead of re-running flaky tests without also running tests which were previously successful.

Other

TheREADME > parallel documentation section currently states:

If you use the GitHub Actions facility forRe-running workflows and jobs, note thatRe-running failed jobs in a workflow is not suited for use with parallel recording into Cypress Cloud. Re-running failed jobs in this situation does not simply re-run failed Cypress tests. Instead it re-runsall Cypress tests, load-balanced over the containers with failed jobs.

To optimize runs when there are failing tests present, refer to optionalCypress Cloud Smart Orchestration Premium features:

• Spec Prioritization
• Auto Cancellation. See alsoSpecify auto cancel after failures for details of how to set this option in a Cypress GH Action workflow.

• See previous issueGithub actions: "Re-run failed jobs" will run the entire test suite #531 for extensive historical and background reading on this issue.