Bazel
This page outlines how the Launchable CLI interfaces with Bazel.
This is a reference page. See Getting started, Sending data to Launchable, and Subsetting your test runs for more comprehensive usage guidelines.

Recording test results

After running tests, point the CLI to your test report files to collect test results and train the model:
1
launchable record tests --build <BUILD NAME> bazel .
Copied!
You might need to take extra steps to make sure that launchable record tests always runs even if the build fails. See Always record tests.

Subsetting your test runs

The high level flow for subsetting is:
    1.
    Get the full list of tests/test paths and pass that to launchable subset with an optimization target for the subset
    2.
    launchable subset will get a subset from the Launchable platform and output that list to a text file
    3.
    Pass the text file into your test runner to run only those tests
To retrieve a subset of tests, first list all the tests you would normally run and pass that to launchable subset:
1
bazel query 'tests(//...)' | launchable subset \
2
--build <BUILD NAME> \
3
--target <PERCENTAGE DURATION> \
4
bazel > launchable-subset.txt
Copied!
    The --build should use the same <BUILD NAME> value that you used before in launchable record build.
    The --confidence option should be a percentage; we suggest 90% to start. You can also use --time or --target; see Subsetting your test runs for more info.
This creates a file called launchable-subset.txt that you can pass into your command to run tests:
1
bazel test $(cat launchable-subset.txt)
Copied!
Last modified 1mo ago