> 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/analytics.md).

# Analytics

The portal's home screen, a scan of coverage and testing activity across your repositories.

Analytics is the portal's home screen. It answers how testing is going across your repositories for the period you pick.

Choose a repository, or all of them, and a period of 7, 30 or 90 days. The repository you choose carries over to the other screens.

### Headline figures

A strip of tiles sums up the period:

* **Flows covered** and **Entry points covered**, the share of your user flows and entry points with tests committed on each repository's default branch.
* **Code changes tested**, the code changes Kerno reviewed.
* **Potential issues caught**, the runs where a test stopped matching its baseline.
* **Tests in your suite**, the tests committed on your default branches.
* **Active developers**, the people who ran Kerno in the period.

Each tile has an info icon that explains what it counts and which branch it reads. Coverage and tests read each repository's default branch. The other tiles count runs on the branch each repository last ran on.

Until a repository's default branch has synced, it counts no tests. When none of the repositories in view has synced, the coverage and suite tiles read **Not synced**, and a notice below the tiles shows how to start syncing from [Integrations](/docs/portal/integrations.md). When only some have synced, **Entry points covered** says how many are not synced yet.

### Cards

Below the tiles, a card for each of these figures shows how it moved over the period and which repositories lead or lag, plus a card of your top users by runs. Each card links to the screen with the detail behind it, such as [Coverage](/docs/portal/coverage.md) for flows and entry points, [Runs](/docs/portal/runs.md) for code changes and potential issues, and [Repos](/docs/portal/repos.md) for your suite.

Until Kerno has discovered your entry points, the screen points you to finish setting up instead.