> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qlty.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Browsing Coverage

Qlty Cloud lets you browse a project's coverage data interactively, drilling from project-wide numbers down to individual lines. Browsing happens through the same per-project navigation that serves maintainability data, so coverage signals show up alongside other quality information for each file.

## Where to browse from

There are three entry points depending on what you're trying to answer:

### Project Overview (Coverage tab)

For a quick snapshot of where coverage stands on the tracked branch, open the project's [Overview](/cloud/projects/overview) page and switch to the **Coverage** tab. You get:

* The project's total coverage percentage and grade.
* The [Trend chart](/coverage/trends) — coverage over the last 30 days.
* The [Hotspots list](/coverage/hotspots) — top files with the lowest coverage.
* A coverage-coloured [Sunburst chart](/cloud/projects/overview#sunburst-chart) for spotting under-covered subtrees at a glance.

### Code view (per-file metrics)

To walk the repository's directory tree with coverage alongside complexity and size, use the project's [Code](/cloud/projects/code) tab. Tree, List, and Unformatted-Files sub-views all expose coverage percentage as a sortable column. Clicking a file opens its metrics page, which includes line-by-line coverage hits.

### Pull Request coverage

To see how a specific change affected coverage, open a PR from the [Pull Requests](/cloud/projects/pull-requests) tab and switch to the PR's **Coverage** sub-tab. That view breaks coverage impact into direct changes, [indirect changes](/coverage/unexpected-changes), and (when multiple coverage tags are uploaded) per-component coverage.

## Filtering by coverage tag

If your project uploads multiple [coverage tags](/coverage/tags) (e.g. `unit` and `integration`), the various views show coverage **per tag** as well as combined. This lets you answer questions like "what's our integration coverage on this file?" independent of unit-test coverage.

## What you need first

All of these views require coverage reports to have been uploaded:

* For project-level views, you need at least one upload on the tracked branch.
* For PR-level views, you need an upload on the PR's head commit.

If a view shows empty data, follow [Setting up Code Coverage](/coverage/quickstart) to wire up uploads from your CI.

## See Also

* [Code Coverage](/coverage)
* [Coverage Trends](/coverage/trends)
* [Coverage Hotspots](/coverage/hotspots)
* [Code view](/cloud/projects/code)
* [Pull Request Coverage](/cloud/projects/pull-requests)