MagicCSharp.Testing 1.0.0

.NET 9.0 This package targets .NET 9.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package MagicCSharp.Testing --version 1.0.0
                    


                    

                
NuGet\Install-Package MagicCSharp.Testing -Version 1.0.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="MagicCSharp.Testing" Version="1.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="MagicCSharp.Testing" Version="1.0.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="MagicCSharp.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 MagicCSharp.Testing --version 1.0.0
                    


                    

                
#r "nuget: MagicCSharp.Testing, 1.0.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 MagicCSharp.Testing@1.0.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=MagicCSharp.Testing&version=1.0.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=MagicCSharp.Testing&version=1.0.0
                    


                            Install as a Cake Tool

MagicCSharp.Testing

Test doubles for the MagicCSharp framework. No test framework dependency, no database, no containers — add MagicCSharp.Testing.Database when you need those.

Type Replaces Why
FakeClock IClock Move time by hand. A thirty-day late fee is testable in milliseconds.
FakeKeyGen IKeyGenService Snowflake ids derived from FakeClock, so ids and timestamps agree.
SyncEventDispatcher IEventDispatcher Runs handlers inline and records them, so you can assert without sleeping.
InMemoryDistributedLockProvider IDistributedLockProvider Real mutual exclusion in-process, re-entrant during inline event dispatch.
TrackingDistributedLockProvider IDistributedLockProvider Grants everything, records the names — for asserting what was locked.

Wiring

var clock = new FakeClock();

services.RemoveAll<IClock>();
services.AddSingleton<IClock>(clock);

services.RemoveAll<IKeyGenService>();
services.AddSingleton<IKeyGenService>(new FakeKeyGen(clock));

services.RemoveAll<IDistributedLockProvider>();
services.AddSingleton<IDistributedLockProvider, InMemoryDistributedLockProvider>();

services.RemoveAll<IEventDispatcher>();
services.AddSingleton<IEventDispatcher>(sp =>
    new SyncEventDispatcher(sp.GetRequiredService<IAsyncEventDispatcher>()));

Asserting on events

clock.SetTime(2026, 3, 1);
await createOrder.Execute(new CreateOrderRequest(userId: 1, productIds: [2, 3]));

Assert.True(events.HasDispatchedEvent<OrderCreated>());
Assert.Single(events.GetDispatchedEvents<OrderCreated>());

One deliberate difference from production

SyncEventDispatcher runs handlers inline, inside whatever lock the emitting use case holds. In production dispatch is fire-and-forget, so handlers run after that lock is released. InMemoryDistributedLockProvider closes the gap: while SyncEventDispatcher is dispatching, a handler re-acquiring a name the emitter holds gets a no-op handle rather than deadlocking. The window is scoped to that one dispatch, so genuinely concurrent flows still get ordinary mutual exclusion.

Product Compatible and additional computed target framework versions.
.NET net9.0 is compatible.  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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on MagicCSharp.Testing:

Package Downloads
MagicCSharp.Testing.Database

Repository integration testing for MagicCSharp against a real PostgreSQL in Testcontainers: one container shared across the suite, a logical database per test class, schema created once, and tables truncated between tests. Separate from MagicCSharp.Testing because it needs Docker, xUnit and Npgsql.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.2 100 9/24/2026
1.0.1 101 9/24/2026
1.0.0 98 9/23/2026