> For the complete documentation index, see [llms.txt](https://kerno.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerno.gitbook.io/docs/portal/team-analytics.md).

# Team Analytics

Team Analytics rolls up every test run across your repositories into coverage, regressions caught, and usage, so you can track how testing is going across your team.

#### Filters

Every view can be narrowed:

| Filter      | What it does                                                                       |
| ----------- | ---------------------------------------------------------------------------------- |
| Repository  | Focus on one repository, or view all of them.                                      |
| Branch      | Focus on a branch, on the Usage and Issues Caught views.                           |
| Time period | Set the window for the dashboard figures and charts. Defaults to the last 30 days. |
| Search      | Find a run by file, method, or URL, on the Usage view.                             |

#### Insights

The dashboard shows four figures for the repository and period you select, each with the change against the previous period:

| Metric                 | What it measures                                               |
| ---------------------- | -------------------------------------------------------------- |
| Endpoint test coverage | The share of discovered endpoints that have at least one test. |
| Tests ran              | The number of test runs in the period.                         |
| Active developers      | How many people on your team ran Kerno.                        |
| Issues caught          | Regressions Kerno caught before they were merged.              |

Two charts below them plot coverage and issues caught over the same window.

#### Usage

Every test run, whether or not it found anything. Alongside the repository, branch, and endpoint, each row names the source file the endpoint lives in, so you can trace a run back to the code.

#### Issues Caught

The regressions Kerno found, one row per run where it rejected a diff. Each row shows the repository and branch, the endpoint, how many differences were detected, how many tests ran, when it happened, and who ran it.

This is the view to point at when someone asks what Kerno has actually prevented.

### What's next

* [Billing](/docs/portal/billing.md) to manage your plan and seats.