Sending data to Launchable

Overview
First, follow the steps in the Getting started guide to install the Launchable CLI, set your API key, and verify your connection.
Then return to this page to complete the two steps for sending data:
1.Recording builds
2.Recording test results
The diagram below diagrams the high-level data flow:
Recording builds
Launchable learns from and selects tests based on the Git changes in a build. To send changes to Launchable, run launchable record build before you create a build in your CI script:
1
launchable record build --name <BUILD NAME> --source src=<PATH TO SOURCE>
Copied!
With the --name option, you assign a unique identifier to this build. You will use this value later when you request record test results. See Choosing a value for <BUILD NAME> for tips on choosing this value.
The --source option points to the local copy of the Git repository (or repositories) used to produce this build, such as . or src. See Data privacy and protection for more info.
Recording test results
Launchable also learns from your test results. After running tests, point the CLI to your test report files to collect test results for the build. Launchable uses the <BUILD NAME> value to connect the test results with the changes in the build:
1
launchable record tests --build <BUILD NAME> <TOOL NAME> <PATHS TO REPORT FILES>
Copied!
The CLI natively integrates with the tools below. Click on the link to view instructions specific to your tool:
​Android Debug Bridge (adb)​
​Ant​
​Bazel​
​Behave​
​CTest​
​cucumber​
​Cypress​
​GoogleTest​
​Go Test​
​Gradle​
​Jest​
​Maven​
​minitest​
​nose​
​NUnit​
​pytest​
​Robot​
​RSpec​
If you're not using any of these, use the generic 'file-based' runner integration, the raw profile for custom test runners, or request a plugin.
Inspecting uploaded test results
You can use launchable inspect tests to inspect uploaded data. This is useful for verifying that you passed the correct report path(s) into launchable record tests. You can also see the values Launchable uses to identify individual tests.
The output from launchable record tests includes a tip to run launchable inspect tests:
1
$ launchable record tests --build 123 gradle reports/*.xml
2
​
3
< summary table >
4
​
5
Run `launchable inspect tests --test-session-id 209575` to view uploaded test results
Copied!
Running that command will output a table containing a row for each test including:
test identifier
duration
status (PASSED/FAILED/SKIPPED)
uploaded timestamp
Note that for brevity, this command does not output stdout or stderr (although they are stored).
Next steps
Once you've started sending your builds and test results to Launchable, you can analyze your flaky tests and start subsetting your test runs.

Using the CLI with a public repository

Choosing a value for <BUILD NAME>

Last modified 1mo ago

Copy link

Contents

Overview

Recording builds

Recording test results

Inspecting uploaded test results

Next steps