# Analyze launch results Source: https://docs.qualflare.com/docs/runs/analyze-results · Last updated: 2026-10-27 Review a launch's results in Qualflare: success rate, failures, retries and flaky tests, case run details and run history, then triage failures across launches. To analyze a launch in Qualflare, open it from **Launches** and read its **Overview** tab, then open the failed case runs on its **Test Cases** tab; you need the Viewer role or higher on the project. ## Before you begin * Requires the Viewer role or higher in the project. * A launch to look at: a [manual run](https://docs.qualflare.com/docs/runs/manual-testing) or results uploaded with [`qf collect`](https://docs.qualflare.com/docs/cli/collect). See [Run tests](https://docs.qualflare.com/docs/runs) for both. ## Review a launch Review a launch from its detail panel. ### Step 1: Open Launches In your project, click **Launches** in the left sidebar. ### Step 2: Open the launch Click the launch you want to analyze. Its detail panel opens. ### Step 3: Read the Overview tab On the **Overview** tab, review: * **Success Rate**: the share of case runs that passed, with a breakdown by status * **Case Retries** and **Slowest Cases** * **AI Analysis**: a summary of the run and its risks. See [AI Launch Analysis](https://docs.qualflare.com/docs/ai/launch-analysis). * **Failures**: failed cases with the first line of their error ### Step 4: Check the header counts In the header, check **Flaky Tests** (tests that passed only after a retry) and **Total Retries**. *Figure: Success Rate counts every finished case run, so skipped, error, timeout and aborted results lower it.* You should see the launch's **Success Rate** and its breakdown by status on the **Overview** tab. ### Understand the success rate Success Rate counts every finished case run, including skipped ones. See [Pass rate calculation](https://docs.qualflare.com/docs/runs/launches#pass-rate-calculation). Qualflare doesn't define what a good rate is. To set your own targets, use **Quality Targets** in **Settings** > **Quality** ([Quality settings](https://docs.qualflare.com/docs/administration/project-settings#quality-settings)). The KPI tiles on the **Overview** page show them. The Overview's **Success Rate** tile counts only passed and failed case runs, so it can be higher than a launch's Success Rate ([Overview dashboard](https://docs.qualflare.com/docs/analytics)). ## Open a case run Open a case run from the launch's **Test Cases** tab: 1. Open the **Test Cases** tab 2. Expand a suite to see its case runs and their statuses. The tab has no status filter. 3. Click any case run to see: * Failure message and stack trace * Steps and attachments, such as screenshots, when the results include them * Duration, environment and branch * **Run History**: the same case in earlier launches *Figure: Expand a suite on the Test Cases tab to see its case runs.* Every field is listed in [Case run detail](https://docs.qualflare.com/docs/runs/launches#case-run-detail) and [Run History](https://docs.qualflare.com/docs/runs/launches#related-runs-section). **View Case Definition** in the case run's **⋯** menu opens the [test case](https://docs.qualflare.com/docs/test-management/test-cases). ## Compare with earlier runs A launch doesn't compare itself with the previous launch. To see which way quality is moving: * Use the KPI tiles on the **Overview** page, which show the change against the previous period * Open a suite's **Run History** tab ([Suite panel](https://docs.qualflare.com/docs/test-management/test-suites#suite-panel)), or a case run's **Run History** section ## Triage failures Triage failures from the launch down to the single case run, then across launches. ### Find the launch On the **Launches** page, filter the list by **Platform**, **Automation**, **Environment** or **Language**, or search ([Filters](https://docs.qualflare.com/docs/runs/launches#filters)). Launches have no assignee. ### Review the failures in a launch 1. Open the launch 2. On the **Overview** tab, check **Failures** and the **AI Analysis** 3. Open the **Test Cases** tab and expand suites to find the failed case runs. The tab has no filter or group-by. ### Drill into a failure 1. Click a failed case run 2. Review **Failure Details**: * **Message**: What went wrong * **Stack trace**: Where it went wrong (for automated tests) 3. Check attachments, such as screenshots, when the results include them 4. Check the **Run History** section to see this case's past results: * Has this test failed before? * When did it last pass? * What changed since then? ### Find related failures Open **Failure Clusters** in the sidebar (available on Starter, Core, Scale, Enterprise). It groups related failures across launches by root cause. See [Failure Clusters](https://docs.qualflare.com/docs/ai/failure-clusters). Track related failures in one defect to avoid duplicate bug reports. See [Create, triage and close defects](https://docs.qualflare.com/docs/defects/manage-defects). ## Retries and flaky tests Qualflare doesn't re-run tests. Set up retries in your test framework or CI job. When your results include retries: * The launch shows **Flaky Tests** (tests that passed only after a retry; see [Flaky test](https://docs.qualflare.com/docs/reference/glossary#flaky-test)) and **Total Retries** * Each case run shows its **Retries** count, with a flaky badge when the test passed after retrying Separately, flaky test detection (available on Starter, Core, Scale, Enterprise, Open Source) looks across recent launches. When a case keeps flipping between pass and fail, Qualflare opens a Medium-severity defect with the flaky category (shown as **Flakiness**, and as **Flaky Test** in the Category filter) and closes it when the case is stable again. Tune it under **Flaky Test Detection** in **Settings** > **Quality**. See [Quality settings](https://docs.qualflare.com/docs/administration/project-settings#quality-settings). ### Interpret a failure * **Consistent failure**: Same test fails again with the same error * Likely a legitimate bug * Create a defect and name the launch and case in its description * **Inconsistent failure**: Test passes on retry * Likely a flaky test * Investigate timing issues, dependency problems, or environmental factors * **Different failure**: Test fails with a different error * Multiple issues may exist * Investigate each failure mode ## Track trends on the Overview page To track trends, open the project's **Overview** page: it shows quality trends over the last 7, 15 or 28 days, and you can filter it by environment. Its tiles and charts are described in [Overview dashboard](https://docs.qualflare.com/docs/analytics). ## Share and export results Sharing and exporting results have their own guide, [Share and export results](https://docs.qualflare.com/docs/runs/share-results). ### Publish a public report On the Open Source plan, publish a project's uploaded launches as a read-only public report. See [Publish a public report](https://docs.qualflare.com/docs/runs/share-results#publish-a-public-report). ### Get launches out of Qualflare Read launches as JSON or CTRF with the REST API, `qf` or MCP. See [Get launches as JSON or CTRF](https://docs.qualflare.com/docs/runs/share-results#get-launches-as-json-or-ctrf). ## Troubleshoot * **The launch is still Pending**: a manual run stays Pending until someone finalizes it; see [Finalize the launch](https://docs.qualflare.com/docs/runs/manual-testing#finalizing-the-launch). An automated launch is Pending when its results include pending tests but no failed or errored ones. * **No AI Analysis on the Overview tab**: manual launches get none. For an upload, see the analysis states in [AI Launch Analysis](https://docs.qualflare.com/docs/ai/launch-analysis). ## Next steps * [Share and export results](https://docs.qualflare.com/docs/runs/share-results): publish a report or read launches as JSON. * [Launches](https://docs.qualflare.com/docs/runs/launches): every status, field and tab of a launch. * [Environments](https://docs.qualflare.com/docs/runs/environments): where each launch ran. * [`qf launches list`](https://docs.qualflare.com/docs/cli/read-commands#launches): list launches from the command line. * [Search, filters and shortcuts](https://docs.qualflare.com/docs/get-started/search-and-filters): filter launches and every list.