Sharded test runs, with a timeline of every shard

Qualflare now understands sharded test runs. Upload the result files from all your shards together and they become a single launch. The new Shards tab then shows how the work was spread across shards, so you can see which shard is slowing the build down.

What's new

• --shard for qf collect. Pass every shard's result file to one qf collect call with --shard, and each file becomes its own shard, numbered from 0 in the order you list them.
• Shards detected automatically. Playwright JSON reports use each test's worker as its shard, and record when each test started. JUnit and pytest reports can set a shard per test with a shard property. You don't need a flag for either.
• The Shards tab. On a launch, Shards shows a Shard Timeline: one row per shard with its case count and duration. Where start times weren't reported, the timeline estimates them from case order and draws them dashed.

How to use it

Collect every shard's results in the same job (for example, download them as artifacts from each shard job), then upload them together:

qf my-app collect shard-0.xml shard-1.xml shard-2.xml --shard

List the files explicitly to keep shard numbers stable. A glob sorts by filename, so shard-10 comes before shard-2.

Availability

Requires qf 0.1.13 or newer. The Shards tab works on every plan.