CriticalTests 3.0.0

<p align="center"> <img src="icon.png" width="96" alt="CriticalTests logo" /> </p>

<h1 align="center">CriticalTests</h1>

<p align="center"> Enforce test contracts for critical classes in .NET. <br/> Mark a class as critical — the pipeline fails if it lacks tests or coverage. </p>

<p align="center"> <img alt="NuGet" src="https://img.shields.io/nuget/v/CriticalTests?style=flat-square" /> <img alt=".NET" src="https://img.shields.io/badge/.NET-netstandard2.0%2B-512BD4?style=flat-square" /> <img alt="License" src="https://img.shields.io/badge/license-MIT-green?style=flat-square" /> </p>

The problem

Large codebases grow without tests. You know which classes are critical — payment processing, authentication, core domain logic — but nothing enforces that they are actually tested. A developer adds a feature, skips the test, the pipeline passes, and a bug ships.

The solution

Mark critical classes with [Critical]. The package automatically fails your pipeline if:

• A critical class has no test class for a declared TestKind
• A critical class falls below its declared minimum coverage

Installation

dotnet add package CriticalTests

Quick start

1. Mark your critical classes

[Critical(TestKind.Unit, TestKind.Integration)]
public class AccountService { }

[Critical("Handles all financial transactions", minCoverage: 80, TestKind.Unit, TestKind.Integration)]
public class PaymentService { }

2. Create criticaltest.json in your test project root

{
  "assemblies": [
    "MyCompany.Core",
    "MyCompany.Domain"
  ]
}

3. Add to your test .csproj

<PropertyGroup>
  <CollectCoverage>true</CollectCoverage>
  <CoverletOutputFormat>json</CoverletOutputFormat>
  <CoverletOutput>./bin/Debug/net5.0/coverage.json</CoverletOutput>
</PropertyGroup>

<ItemGroup>
  <Content Include="criticaltest.json">
    <CopyToOutputDirectory>Always</CopyToOutputDirectory>
  </Content>
</ItemGroup>

4. Write test classes following the naming convention

public class AccountServiceUnitTests { ... }
public class AccountServiceIntegrationTests { ... }

5. Run the pipeline in two stages

# Stage 1 — run tests and generate coverage report
dotnet test --filter "FullyQualifiedName!~CriticalContractTests"

# Stage 2 — validate contracts against the coverage report
dotnet test --filter "FullyQualifiedName~CriticalContractTests" --no-build

[Critical] attribute

public enum TestKind { Unit, Integration, Load }

Naming convention

The validator expects test class names to contain both the production class name and the TestKind:

Pipeline output on violation

TEST CONTRACT VIOLATED
  MyCompany.Core.Services.AccountService => missing test class of type [Integration]

INSUFFICIENT COVERAGE IN CRITICAL CLASSES
  x MyCompany.Core.Services.PaymentService: current = 75%  |  required = 80%

GitHub Actions example

- name: Run tests and collect coverage
  run: dotnet test --filter "FullyQualifiedName!~CriticalContractTests"

- name: Validate critical contracts
  run: dotnet test --filter "FullyQualifiedName~CriticalContractTests" --no-build

Documentation

• Package Overview — architecture, components and pipeline flow
• Usage Guide — step-by-step setup and examples

License

MIT