> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/guides/test-orchestration.md). # Test Orchestration The better alternative to Playwright Sharding Scaling a test suite comes with many challenges. As the test suite grows, CI becomes slower. Playwright [parallelism](https://playwright.dev/docs/test-parallel) helps reducing the bottleneck, but they aren't as efficient as they could be. Sharding splits test files based on the lexical order of file paths, leading to unbalanced workloads. Currents Test Orchestrator fixes that by balancing the load using historical execution data, continuously creating the most optimal execution order for test runs, resulting in [up to 40% reduction the CI execution time](https://currents.dev/posts/currents-and-fundguard) with minimal changes to configuration.

Instead of pre-allocating tests to CI nodes, the orchestrator keeps a live queue of pending tests and dynamically assigns them to machines as they become available. This allows continuous communication and coordination across all nodes, improving overall throughput. * **Learning from history** - tracks test durations and uses that data to improve distribution in future runs. * **No renaming hacks** - you don’t need to rename spec files or manually tune splits for better balance. * **Dynamic test distribution** - tests are split based on real-time machine availability, not pre-assigned upfront. * **Handles CI quirks** - automatically adapts to runner spin-up delays or unresponsive machines. * **Scales with your suite** - maintains high throughput as test count, duration, or structure evolves. * **Your CI, your environment** - the tests are running on your existing environment, the orchestrator client communicates with Currents for task assignments and reporting the results. * **It's just Playwright** - an orchestrator uses Playwright internally, using the same configuration and interfaces to run the tests. ### Get Started

			Cover image
Technical Deep Dive	^{Fully understand how Test Orchestration works and how it compares to native Playwright Sharding.}	Playwright Parallelization	currents-orchestration-queue.png
Setup Orchestration	^{Read the guide on how to setup Test Orchestration in your test suite.}	Orchestration Setup	playwright-logo-neo.png

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.currents.dev/guides/test-orchestration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.