Test Launches - Track Execution Results & Analytics

Track test execution results with launches. Understand launch lifecycle, sources (manual vs CLI), analytics, and how to monitor pass rate trends in Qualflare.

Launches

A launch is a test execution event that captures the results of running tests.

What is a Launch?

When you run tests in Qualflare, the execution is recorded as a launch. A launch contains:

Source: Manual execution or CI/CD automation
Environment: Where tests ran (dev, staging, production)
Time: When the launch occurred
Results Summary: Pass/fail counts, duration, status
Case Runs: Individual results for each test case executed

Launch Lifecycle

Launches progress through these states:

Running: Tests are currently executing
Completed: All tests finished, results available
Failed: Launch encountered an error (not test failures, but system errors)

Launch Sources

Manual Launches: Created by testers running tests through the UI. Used for ad-hoc testing, exploratory testing, or on-demand verification.

CLI Launches: Generated automatically when test results are uploaded via the Qualflare CLI. This is the typical CI/CD integration pattern:

qf collect results.xml --project "MyApp" --launch "CI Build #123"

Launch Components

Each launch contains:

Metadata: Source, environment, duration, timestamp
Summary: Total tests, passed, failed, skipped, pass rate
Case Runs: Individual results for each test case executed
Logs and Artifacts: Screenshots, error logs, test output
Trends: How this launch compares to previous runs

Tests often run across multiple parallel workers to finish faster — a shard represents one of those workers within a single launch. When a launch is collected with shard information, each case run carries a shardIndex, and the Launch Detail view shows a Shards tab visualizing how work was distributed and how long each worker took.

Shard data comes from either:

The CLI's --shard flag, which numbers each uploaded file as a shard by argument position.
Auto-detection: some frameworks (JUnit-family, pytest, Playwright) report which worker ran a test natively, so no flag is required.

See Reference: Launches — Shards for what the timeline view looks like, and CLI: Sharding Parallel Test Runs for upload details.

Launch Analytics

Qualflare tracks launch history to show:

Pass Rate Trends: Are you improving or regressing over time?
Flaky Tests: Which tests fail inconsistently?
Execution Time: How long do test runs take?
Failure Patterns: Common failure modes across launches

Case Runs - Individual test results within a launch
Test Plans - Scheduled launches
Defects - Bugs linked from failed launches
Launches CLI Commands - Query launch records from the command line