AutoDispatch.Testing 1.5.0

.NET 8.0 .NET Standard 2.0

dotnet add package AutoDispatch.Testing --version 1.5.0

NuGet\Install-Package AutoDispatch.Testing -Version 1.5.0

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="AutoDispatch.Testing" Version="1.5.0" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="AutoDispatch.Testing" Version="1.5.0" />
                    

                            Directory.Packages.props

<PackageReference Include="AutoDispatch.Testing" />
                    

                            Project file

For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.

paket add AutoDispatch.Testing --version 1.5.0

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: AutoDispatch.Testing, 1.5.0"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

#:package AutoDispatch.Testing@1.5.0

#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.

#addin nuget:?package=AutoDispatch.Testing&version=1.5.0
                    

                            Install as a Cake Addin

#tool nuget:?package=AutoDispatch.Testing&version=1.5.0
                    

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

AutoDispatch.Testing

Lightweight test helpers for AutoDispatch.Generator — no DI container, no ASP.NET Core host required.

Installation

dotnet add package AutoDispatch.Testing

FakeServiceProvider

A minimal IServiceProvider test double, useful for constructing the generated Dispatcher or testing AddAutoDispatch() consumers directly:

var sp = new FakeServiceProvider()
    .Add(new CreateOrderHandler())
    .Add(new LoggingBehavior<CreateOrderCommand, OrderId>());

IDispatcher dispatcher = new Dispatcher(sp);
var orderId = await dispatcher.SendAsync(new CreateOrderCommand("cust-1"));

PipelineTestHarness

Test a [Behavior] in isolation — short-circuit next() to a known result and assert the behavior's own logic:

var behavior = new LoggingBehavior<CreateOrderCommand, OrderId>(logger);

var result = await PipelineTestHarness.InvokeAsync<CreateOrderCommand, OrderId>(
    behavior.HandleAsync,
    new CreateOrderCommand("cust-1"),
    nextResult: new OrderId(Guid.NewGuid()));

Or compose multiple behaviors + a handler exactly like the generated dispatcher does, without any DI setup:

var result = await PipelineTestHarness.InvokeAsync<CreateOrderCommand, OrderId>(
    command,
    handler: () => handler.HandleAsync(command),
    ct: CancellationToken.None,
    loggingBehavior.HandleAsync,
    validationBehavior.HandleAsync);

Why not reference `IDispatcher`/`IPipelineBehavior<,>` directly?

AutoDispatch generates its attributes and interfaces locally into each consuming project — there is no shared runtime assembly (that's what makes it AOT/reflection-free). Because of that, PipelineTestHarness works against plain delegates (via method-group conversion, e.g. behavior.HandleAsync) rather than the generated interface type, so it works identically no matter which project generated the type.

Product	Compatible and additional computed target framework versions.
.NET	net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed.
.NET Core	netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed.
.NET Standard	netstandard2.0 is compatible. netstandard2.1 was computed.
.NET Framework	net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed.
MonoAndroid	monoandroid was computed.
MonoMac	monomac was computed.
MonoTouch	monotouch was computed.
Tizen	tizen40 was computed. tizen60 was computed.
Xamarin.iOS	xamarinios was computed.
Xamarin.Mac	xamarinmac was computed.
Xamarin.TVOS	xamarintvos was computed.
Xamarin.WatchOS	xamarinwatchos was computed.

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

.NETStandard 2.0
- No dependencies.
net8.0
- No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last Updated
1.5.0	107	7/28/2026