Recording test results with the Launchable CLI

Subsetting with the Launchable CLI

Details about how Launchable integrates with dotnet test.

dotnet test

Product Overview

Getting Started

Using the Launchable GitHub Action

Using CI Integrations

Using test runner integrations

Using the CLI with a public repository

Updating tokenless authentication to use GitHub OIDC

Getting started with the Launchable CLI

Converting test reports to JUnit format

Ensuring record tests always runs

Managing complex test session layouts

Using 'flavors' to run the best tests for an environment

Choosing a value for <BUILD NAME>

Recording builds from multiple repositories

Running under restricted networks

Dealing with shallow clones

Recording builds with the Launchable CLI

Using the Launchable CLI

Sending data to Launchable

Planning your subset implementation

"Training wheels" mode with the --rest option

Observing subset behavior

Choosing a subset optimization target

Subsetting with test runner integrations

Requesting and running a subset of tests

How Launchable selects tests

Viewing time savings

Predictive Test Selection

Trends

Flaky Tests

Unhealthy Tests

Test Insights

Test results and reports

Test notifications via Slack

Features

Object model

Organization

Workspace

Build

Test Session

Subset

Insight

Concepts

CLI reference

Android Debug Bridge (adb)

Bazel

Behave

CTest

cucumber

Cypress

`file` profile for unsupported test runners

GoogleTest

Go Test

Gradle

Jest

Maven

minitest

nose (Integration)

prove for Perl

pytest (Integration)

`raw` profile for custom test runners

Robot

RSpec

Integrations

.NET

Java

JavaScript

Perl

Python

Ruby

Supported languages

Appium

Cucumber

JUnit

nose

NUnit

Selenium

TestNG

Supported test frameworks

GitHub Actions

CI tool integrations

Troubleshooting

Launchable product rollout

Resources

Data examples

Data privacy and protection

Security policies

Policies