LAUNCHABLE_TOKEN
environment variable in your CI process. How you do this depends on your CI system:launchable-config
is a command-line tool to generate and validate configuration files. The Launchable pytest plugin uses this config..launchable.d/config.yml
file in the current directory that looks like this:.launchable.d/config.yml
:source
option in the record-build
section points to your Git repository (the default is .
, the current directory).mode
option in the subset
section is set to record-only
.launchable.d/config.yml
file:--launchable
option to the pytest command. It is very easy:--launchable-conf-path
option:launchable-test-result
by default.launchable.d/config.yml
:source
option in the record-build
section points to your Git repository (the default is .
, the current directory).mode
option in the subset
section is set to subset
or subset_and_rest
based on your needs​.launchable.d/config.yml
file:--launchable
option to the pytest command. It is very easy:--launchable-conf-path
option:subset_and_rest
mode is chosen)launchable-test-result
by default--junit-xml
option, e.g.:junit_family=legacy
as the report format. pytest has changed its default test report format from xunit1
to xunit2
since version 6. See Deprecations and Removals — pytest documentation. The xunit2
format does not output the file name in the report, and the file name is required to use Launchable.--json
option.launchable record tests
always runs even if the build fails. See Always record tests.launchable subset
with an optimization target for the subsetlaunchable subset
will get a subset from the Launchable platform and output that list to a text filelaunchable subset
:--build
should use the same <BUILD NAME>
value that you used before in launchable record build
.--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.launchable-subset.txt
that you can pass into your command to run tests: