> ## Documentation Index > Fetch the complete documentation index at: https://docs.peepsai.com/llms.txt > Use this file to discover all available pages before exploring further. # Read a release report > See how a release went at a glance: its results, an unconfirmed AI analysis, key facts, the comparison with an earlier release, coverage and run health. A release report shows every result in one release of a project. It counts each test's latest result per configuration, so a retry replaces the result before it rather than adding to the count. Open **Releases** in the sidebar, under **Runs**, and pick a release. Anyone in your organization can read a report. > [!NOTE] > > A configuration is what your results ran on, such as a browser or a device. Your project names it, so the report says **Browsers** or whatever your project calls them. The examples on these pages use a storefront project that names them **Browser**. ![The top of the report for release 2.14.0: 87 results on 3 browsers with a bar of 68 passed, 11 failed, 3 errors, 3 skipped and 2 N/A, an AI analysis card marked Unconfirmed with three highlights, and four key facts: To review, Browsers failing, Compared with 2.13.0 and Coverage.](https://mintcdn.com/peeps-ai/dn4jpKrOiHjTnw5R/images/releases/report-opening.png?fit=max\&auto=format\&n=dn4jpKrOiHjTnw5R\&q=85\&s=a830af52a3fb78f46c0518b6f446e374) ## The results The line under the release's name says how many results it holds and on how many configurations. The bar and the counts under it split them by outcome, and the line above the bar's right end gives the pass rate: passed results out of those decided, meaning passed, failed or errored. When some results aren't linked to a test case, the bar includes them and the pass rate doesn't, and the line says so. Select the info icon for what the counts mean. When one issue holds a large share of the failures, the report names it, such as **8 of 14 failures are one issue**, with a **View issue** link. Short notes appear under the results only when they apply: | Note | When it appears | | - | - | | **No linked failures** | Results failed, but none of them is linked to a test case. | | **Failed because of the test environment** | Your results reported failures from the test environment rather than the product. | | **Still being analyzed** | Failure analysis hasn't finished. Those results count as failed, and group titles may change. | | **Failure analysis is off** | Your organization has turned it off. | | **Treated as one** | Results with the same test and no configuration count as one, and the latest replaces the rest. | A **things worth a look** link goes to [Run health](#run-health) when it lists anything. ## AI analysis The **AI analysis** card summarizes the failures and lists highlights, each linked to its test case. Select **Read more** for the rest. The analysis is always marked **Unconfirmed**. It suggests where to look, and any cause it names is a lead to check, not a finding. It never changes a result or clears a failure. Whether to ship is your decision. A note says so when it was written before the latest results. ## Key facts Four or five facts sit under the analysis. Some numbers are links or filters. | Fact | What it shows | | - | - | | **To review** | How many issues the release has and how many are reviewed. **No earlier record** and **seen before** split them by history. **No earlier record** may only mean Peeps has no history for it. Selecting either [filters the report](https://docs.peepsai.com/releases/filter-and-share.md#issue-selectors). | | **Configurations failing** | How many configurations have a failure, and which has the most. Carries your project's name for them. | | **Your tracker's name** | Shown only when your organization has [connected Linear or Jira](https://docs.peepsai.com/mcp/issue-trackers.md). How many issues are tracked, **failed since done** and **not tracked**. Each is a filter. | | **Compared with** | How many results are newly failing, fixed and still failing against an earlier release. Links to [Comparison](#comparison). | | **Coverage** | How many of the project's test cases ran. Links to [Coverage](#coverage). | Below these sit the report's [three tabs](https://docs.peepsai.com/releases/find-what-failed.md). ## Comparison **Comparison** shows what changed against another release. **Compare with** picks the release; it starts on the nearest earlier release that shares a result with this one. ![The Comparison section against 2.13.0: 11 more failures and a pass rate down 12 points, a bar for each release, and under What changed 9 newly failing, 1 fixed and 2 still failing, each listing test cases, then a Missing browsers list.](https://mintcdn.com/peeps-ai/dn4jpKrOiHjTnw5R/images/releases/comparison.png?fit=max\&auto=format\&n=dn4jpKrOiHjTnw5R\&q=85\&s=ee4240b3191f2bad69c64d0486ec4e0c) * **Newly failing**, **Fixed** and **Still failing** list the results that changed, or didn't, with the test cases they belong to. * **Missing** and **New** configurations list those in only one of the two releases, under your project's name for them. They appear only when the two differ. * **Recent releases** shows other releases' pass rates beside this one's, so you can see the trend. When the two releases share no result, the section says so and asks you to pick another release. ## Coverage **Coverage** says how many of the project's test cases ran in this release, and how many of those linked to a result have a failure. A bar for each top-level folder shows the same count per folder, when your test cases are in folders. ![The Coverage section: 25 of 25 cases ran, 100%, 8 of 25 linked test cases have a failure, with a full bar each for Accounts, Search, Settings and Checkout.](https://mintcdn.com/peeps-ai/dn4jpKrOiHjTnw5R/images/releases/coverage.png?fit=max\&auto=format\&n=dn4jpKrOiHjTnw5R\&q=85\&s=df993a5819454c41d4df085bebbe2cf5) ## Run health **Run health** says whether every result is filed and whether its analysis settled. It lists only what needs a look, one row per item, each with a short status and what it means. | Part | Rows you may see | | - | - | | **Results filed** | Uploads still applying or failed, sessions still running or that didn't finish, tests still being filed or waiting to retry, tests to map, files that look like a duplicate, files missing or rejected, results not filed under a case. | | **Analysis** | Failure analysis still running, waiting a long time, failed or off. | A spinner marks a row Peeps is working on, and its count updates as results arrive. Rows without one need a look, or are waiting on a person. Rows can link to the sessions they're about or open the questions they need answered. When a part has nothing to report it says **All results filed** or **Analysis settled**. When neither has, the card says **Ran cleanly**. ![The Run health card with a spinner on three rows: 1 upload still applying, 2 sessions still running with a View sessions link, and failure analysis still running for 12 results.](https://mintcdn.com/peeps-ai/dn4jpKrOiHjTnw5R/images/releases/run-health-running.png?fit=max\&auto=format\&n=dn4jpKrOiHjTnw5R\&q=85\&s=7a19601f313e8b72fc4fb3f63bcb5120) While results are arriving ![The Run health card reading Ran cleanly: all 11 sessions finished and every result is filed.](https://mintcdn.com/peeps-ai/dn4jpKrOiHjTnw5R/images/releases/run-health-settled.png?fit=max\&auto=format\&n=dn4jpKrOiHjTnw5R\&q=85\&s=3cae76d2eae2bdee1f39137ba8b6eb5a) When everything is filed ## Further down the page * **Not linked to a case yet** lists results Peeps can't file under a test case, when there are any. Contributors can map them from here. * **Configurations in this release** lists each configuration. It carries your project's name for them. * **Runs** lists the batches, manual runs and single runs in the release. See [Add runs to a release](https://docs.peepsai.com/releases/add-runs.md). * **Sessions** lists the sessions that sent results, with anything your test harness reported about them. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.