ZeroAlloc.Validation.Testing 2.3.3

ZeroAlloc.Validation

Source-generated, attribute-based alternative to FluentValidation for .NET: no reflection, 0 bytes allocated when a model is valid, and NativeAOT-ready.

Why ZeroAlloc.Validation

• Nothing allocated on the valid path. A passing validation allocates 0 B, asserted by allocation regression tests for flat, nested and collection models. FluentValidation 12 allocates 696–3,528 B for the same models.
• 27.8–133.2× faster than FluentValidation 12 on the valid path, measured side by side in the same BenchmarkDotNet run.
• Works under NativeAOT and trimming. The validator is plain generated C#, with no reflection or expression trees; CI publishes and runs a NativeAOT sample on every build.
• Mistakes surface at compile time. A numeric rule on a string, an [IsInEnum] on a non-enum or a [CustomValidation] method with the wrong signature fails the build, not a request.

Install

dotnet add package ZeroAlloc.Validation

The source generator ships inside this package; nothing else is required.

Quick start

using System;
using ZeroAlloc.Validation;

var validator = new CreateOrderRequestValidator(); // generated at build time
var result = validator.Validate(new CreateOrderRequest { Reference = "", Amount = 0, Email = "nope" });

if (!result.IsValid)
    foreach (ref readonly var f in result.Failures)
        Console.WriteLine($"{f.PropertyName}: {f.ErrorMessage}");

[Validate]
public class CreateOrderRequest
{
    [NotEmpty, MaxLength(50)] public string  Reference { get; set; } = "";
    [GreaterThan(0)]          public decimal Amount    { get; set; }
    [NotEmpty, EmailAddress]  public string  Email     { get; set; } = "";
}

Mark a model with [Validate] and the generator writes CreateOrderRequestValidator for you. Running it prints:

Reference: Reference must not be empty.
Amount: Amount must be greater than 0.
Email: Email must be a valid email address.

What you get

• 20 built-in rules as attributes: emptiness, equality, ranges, lengths, regex, e-mail, enums, precision and scale.
• Your own rules through reusable attributes, inline [Must] predicates or [CustomValidation] methods.
• Asynchronous rules, awaited by the generated ValidateAsync.
• Nested objects and collections, with property paths such as Items[0].Sku in the failures.
• Rules inherited from base types, conditional rules with When, Unless and [SkipWhen], and short-circuiting with [StopOnFirstFailure].
• Per-rule severity, Error, Warning or Info, and custom error messages with placeholders.
• Pipeline behaviors that wrap validation calls, without a per-call allocation.

Optional packages:

• ZeroAlloc.Validation.AspNetCore: validates request models automatically and returns HTTP 422 on failure.
• ZeroAlloc.Validation.Inject: registers every validator in DI with one AddZeroAllocValidators() call.
• ZeroAlloc.Validation.Options: validates Microsoft.Extensions.Options at startup with ValidateWithZeroAlloc().
• ZeroAlloc.Validation.Testing: fluent assertions for unit-testing validators.

Performance

Valid path, FluentValidation 12.1.1, measured 2026-10-15. Allocations are exact. Speed is shown as same-run ratios, because the benchmark host is a shared VM; absolute timings are not published. On the invalid path ZeroAlloc is 12.7–62.9× faster and allocates 12.4–74.9× less. See Performance for the full results.

Learn more

• Documentation: validation.zeroalloc.net, including the attribute reference and the diagnostics list.
• Upgrading from v1: Migrating to v2 and the changelog.

Related ZeroAlloc packages:

• ZeroAlloc.Mediator (docs): its ZeroAlloc.Mediator.Validation package runs these validators on every request before the handler.
• ZeroAlloc.Results (docs): a Mediator request that returns Result<T, ValidationError> gets a failed validation back as a failure result, not an exception.
• ZeroAlloc.Pipeline (docs): the pipeline-behavior model this library's validator behaviors are built on.
• ZeroAlloc.Authorization (docs): plugs into the same Mediator pipeline and runs before validation, so a denied caller sees no validation errors.

Contributions are welcome: open an issue or a pull request. Licensed under MIT.