# Split CI test suites with historical timing data (beta) (https://depot.dev/changelog/2026-07-15-test-splitting)

> Published 2026-07-15

Depot can now split a test suite across CI shards using durations from your earlier test reports. Give each shard the same candidate list, and Depot assigns a time-balanced, non-overlapping subset of candidates.

Test splitting builds on the [test results beta](/changelog/2026-06-02-test-results-beta) and reads timing data from the same JUnit reports. No separate setup needed: `depot tests run` uploads a report on each run. Both are free to use while in beta.

The new `depot tests run` command runs your test command and uploads its JUnit reports in one step. Use it directly from your CI shell or with [`depot/tests-run-action`](https://github.com/depot/tests-run-action). Configure a matrix or parallel CI steps and Depot balances candidates using their recorded durations. Use `depot tests split` when you only need a shard's split results and want to pass them to your test runner yourself.

New suites run without timing data, then become better balanced as reports accumulate.

Read the [Split tests by timing](/docs/ci/how-to-guides/split-tests) guide for a complete matrix example.

## For AI Agents

The full site index is at [llms.txt](https://depot.dev/llms.txt). Append `.md` to any documentation, blog, changelog, or customer URL to fetch its markdown source directly.