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

# Coverage

Every user flow and entry point Kerno tests, which ones have tests today, and how to mark the critical ones.

Coverage lists the [user flows](/docs/core-concepts/user-flows.md) and entry points Kerno tests, and which ones have tests today, across all branches. Pick a repository to narrow it down.

### User flows

The user flows table lists each flow your agent mapped, with its number of steps and its last run. A flow counts as covered once its own flow test has finished a run, on any branch. Filter by covered or not covered, or search by name.

Select a flow to open its panel, which shows the outcome the flow should reach, its steps in order, marked as under test or setup, how its test changed over time and its run history. Select a step to open that entry point.

### Entry points

The entry points table lists every HTTP route, MCP tool and background consumer Kerno discovered. Each row shows whether the entry point has a baseline, how many user flows use it, and its last run. Filter by kind, by whether it is part of a flow, or by whether it is critical, and add columns such as the testing mode, the number of tests or the source file.

Select an entry point to open its panel, which shows its latest run, the flows it is part of, how its tests changed over time and its full run history.

### Critical entry points

Use the **Critical** switch on an entry point to mark it as critical for your team. Kerno always tests a critical entry point at high effort, whatever effort your agent asks for, and the mark is saved in your repository. An entry point Kerno no longer discovers can't be marked.