Why CoverBouncer? Standard coverage tools give you one number — but not all code is equal. Your payment logic needs 90%+ coverage while your DTOs might not need any. CoverBouncer lets you enforce different thresholds for different parts of your codebase using fully customisable profiles.

Key Features:

• 🎯 Profile-based coverage — tag files with [CoverageProfile("Critical")] and set per-profile thresholds
• 🤖 Smart tagging — interactive, batch, and auto-suggest modes via the CLI
• 🔌 Drop-in MSBuild integration — works with your existing dotnet test
• 🔍 Filtered run awareness — --filter runs skip untargeted files automatically
• 🚫 CI/CD ready — blocks merges when coverage drops below thresholds
• ⚙️ Zero-config start — untagged files default to NoCoverage, adopt gradually

Links: GitHub Repository · NuGet Package

Quick start: dotnet add MyApp.Tests package CoverBouncer.MSBuild → dotnet coverbouncer init → tag your critical files → dotnet test. Coverage policy enforced automatically.

I always have something in the pipeline. The tools I build for clients often surface patterns that deserve a public, open-source solution — and when they do, they end up here. If you've got an idea for a developer tool or see a gap that needs filling, I'm always open to collaborating.

Interested in collaborating? Get in touch and let's build something useful together.