Comment on page

Playwright Parallelization

Playwright tests parallelization using shards and reporting the results to Currents

Parallelization in Playwright

By default, Playwright runs the test files in parallel using several worker processes that run on the same machine (see Playwright docs). In addition to machine-level parallelization with workers, you can split the spec files between multiple machines using sharding.

What is Playwright Sharding?

As mentioned, Playwright runs test files in parallel by default, but you can scale this behaviour by running tests on multiple machines simultaneously. This is called sharding in Playwright.
Running Playwright tests with sharding enabled
This behaviour is activated by using the --shard flag. For example:
npx playwright test --shard 1/2
Currents collects test results across different machines + workers and presents them in the cloud dashboard, using CI Build ID to assign the results to a build/run.

How does Playwright sharding work?

Running Playwright tests in parallel in a CI environment involves creating multiple containers. Depending on the size of your browser test suite, it can be dozens or hundreds of containers. This will depend on the shards that you declare for your set of tests, but remember that the tests inside each shard will be also parallelized amongst multiple workers.
The workers on each shard will report to Currents the outcome of the tests.

Do I need my machines to run Playwright sharding?

Yes. You still need CI machines that will run the actual tests. Currents Dashboard will record test results to allow troubleshooting of your Playwright tests.

How to run Playwright tests with sharding enabled locally?

Running Playwright tests with sharding enabled on localhost requires running two or more executions of Playwright tests with the --shard flag and the same CI Build ID.
Open two separate terminals and run an identical pwc command with --shard=1/2 and --shard=2/2 flag respectively and --ci-build-id flag with identical values in both terminals. In the example below we use a dummy CI build ID ciid, you can replace it with any value as long as it's the same.
npx pwc --key <currents key> --project-id <currents project id> --ci-build-id ciid --shard=1/2
npx pwc --key <currents key> --project-id <currents project id> --ci-build-id ciid --shard=2/2
You will see that two shards are executing different spec files and running in parallel as well as the amount of workers executing tests on each one of the shards.

Splitting Playwright spec files for sharding

You don't need to split files manually when using Playwright / Currents dashboard service - Playwright does that for you automatically and distributes the spec files between Playwright shards and workers.
By default, Playwright runs test files in alphabetical order and distributes the files between shards and workers on each shard. You can use some naming convention to control the test order, for example:
  • 001-user-signin-flow.spec.ts
  • 002-create-new-document.spec.ts
and so on.
In addition, you can enable parallel test execution in a single file, so Playwright will split individual tests instead of test files. Please note, that Currents support of parallel test execution in a single file is in active development (as of November 2023).

What CI providers can run Playwright sharding?

Any CI provider or tool that allows creating multiple containers/jobs can be integrated with Currents for running Playwright sharding.
Here are a few example repositories for popular CI providers:

What is CI Build ID?

The CI Build ID defines what build (or run) the results belong to - for example, providing the same CI Build ID on two different machines will show their results in the same run.
The value of this flag is calculated automatically for popular CI tools, but you can also provide it explicitly. See CI Build ID guide for details.
You can provide CI Build ID using the environment variable: CURRENTS_BUILD_ID, pwc CLI flag
npx pwc ... --ci-build-id XXXXX
or inline configuration:
// playwright.config.ts
import { currentsReporter } from '@currents/playwright';
reporter: [
ciBuildId: process.env.CURRENTS_CI_BUILD_ID