Starting today, the --variant
option should be used to upload test results when the same tests are run on different environments.
If you run the same CI tests on different architectures or environments, test flakiness could be unique to an environment. Examples include testing a mobile app on iOS and Android, running tests for your CLI tool on macOS and Linux, or performing the same e2e tests on different browsers. Tests run on separate environments must be treated as unique to guarantee accurate flake detection.
Using variants, Flaky Tests will now treat the same test run on different environments as unique. This means flakes can be detected and quarantined on a per-environment basis.
A build matrix (or matrix strategy) lets CI run a job across many combinations of variables—like OS, language versions, or dependencies—so you can test your code in every relevant environment.
To specify a variant during upload, use the --variant
option:
1./trunk flakytests upload --junit-paths "test_output.xml" \2--org-url-slug <TRUNK_ORG_SLUG> \3--token $TRUNK_API_TOKEN \4--variant linux_x86_64
Variant names are visible in brackets on your Flaky Tests dashboard:

See the reference docs for more information on uploading test reports with variants.