coverage · git:20261103.f65486c · 2026-11-03 · sha256 31e7d72ab618ef58
coverage git:20261103.f65486cA
Immutable. This exact content never changes and is served at /api/v1/blob/31e7d72ab618ef58.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_yzmubseej4t4zchj/31e7d72ab618ef58e5053b08a1f01d43aacc9b0eb09629287500b678f7c35408.json
Then /plugin install coverage@markdownregistry-yzmubseej4t4zchj in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: coverage
description: The 95% line coverage gate - what counts, what is excluded and why, and how to measure it locally the same way the pipeline does. Use when coverage fails, when adding code that is hard to test, or before opening a pull request.
metadata:
scope: shared
---
# Coverage
## The rule
Total line coverage across every test project, merged into one report, must be at least 95%. The pipeline fails below that, and nobody lowers the number. Coverage comes from Coverlet (`coverlet.msbuild`).
Excluded on purpose, and only these:
| Excluded | How | Why |
| --- | --- | --- |
| `Program.cs` | `ExcludeByFile` | Startup glue, exercised by integration tests but not meaningfully measurable |
| `Migrations/*.cs` | `ExcludeByFile` | Generated by EF Core |
| `obj/**` and `[GeneratedCode]` | `ExcludeByFile`, `ExcludeByAttribute` | Source generators (Mediator, Mapperly, JSON) |
| Wiring and plain models | `[ExcludeFromCodeCoverage]` on the class | Dependency registration (`DependencyInjection`), startup extensions, database models with no logic |
## Steps
1. Measure locally with the same settings as the pipeline (run from the repository root):
``` bash
dotnet test -m:1 \
-p:CollectCoverage=true -p:CoverletOutput=../results/ -p:MergeWith="../results/coverage.json" \
-p:CoverletOutputFormat=opencover%2cjson \
-p:ExcludeByFile="**/Program.cs%2c**/Migrations/*.cs%2c**/obj/**/*.cs" \
-p:ExcludeByAttribute="GeneratedCodeAttribute"
```
The last table printed shows the merged total.
2. Uncovered lines? Write a test for the behaviour (`unit-tests`, `integration-tests`). Branches that can't happen usually mean the code can be simpler.
3. Use `[ExcludeFromCodeCoverage]` only for wiring and plain data classes, never for code with decisions in it.
## Don't
- Lower the threshold, or add a file pattern to the exclusions to get green.
- Add `[ExcludeFromCodeCoverage]` to a handler, validator, repository, endpoint or mapper.
- Write tests that execute lines without asserting anything.
## Check
The command in step 1, or push and read the Test row of the pipeline's Summary comment.