Orchestrated runs

Re-run only failed Playwright tests when using Currents Orchestration

Failed orchestrated reruns require Rerun All Jobs in the CI provider, not Rerun Failed Only.

Orchestrated runs work differently from native Playwright sharding. Currents assigns tests to all available machines. More machines can run the tests faster, and the total number of CI machines does not need to be set in advance.

Rerunning failed-only Playwright tests using Currents Orchestration

That's why failed orchestrated CI reruns use Rerun All Jobs instead of Rerun Failed Only:

• The CI provider will spin up all the containers

• Currents will assign the failed tests to all the available containers

• More available containers will run the tests in parallel faster

Orchestration flow

In Orchestration, Playwright filter flags such as --last-failed belong on pwc-p discover. The generated test list is passed to pwc-p run with --pwc-discovery-file.

npx pwc-p discover --pwc-discovery-file tests.txt --last-failed
npx pwc-p run --key <record-key> --project-id <project-id> --ci-build-id <ci-build-id> --pwc-discovery-file tests.txt

See Orchestration Setup for setup details.

Step-by-step guides

• GitHub Actions — Orchestrated runs

• GitLab CI — Re-run Only Failed Tests

• Jenkins Pipeline — Jenkins

See also the overview: Re-run Only Failed Tests.