Playrunner can now turn one Playwright node into a complete sharded test run. It discovers the suite, chooses a capacity-aware execution plan, starts the shards concurrently, and merges their results into one report.

You set the limits. Playrunner decides how much parallelism the suite can use.

GitHub Actions is a great place to run Playwright tests. For small and medium suites, a standard hosted runner may be all you need.

But browser testing is a compute-heavy workload. As suites grow, teams can reach a point where adding more tests or more Playwright workers does not make CI faster. It can make it slower, less predictable, and sometimes more flaky.

The problem is not GitHub Actions or Playwright. It is the amount of compute available to the workload.

End-to-end tests are most useful when they run at the point where a team decides whether to ship. The Playrunner CLI lets a CI/CD job start a saved workflow, stream its progress, and fail the job when the workflow does not complete successfully.

That turns a Playrunner workflow into a quality gate without rebuilding the workflow as a long collection of pipeline-specific steps.

Today, we're releasing Playrunner, an early source-available visual orchestration platform for teams running Playwright test automation.

Playwright is excellent at executing browser tests. But as a test suite grows across a team, the work around those tests grows too: CI scripts, runner infrastructure, environment configuration, reports, alerts, retries, and issue workflows. Playrunner brings that orchestration layer into one place.