Stratara.Testing 4.0.3

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Stratara.Testing --version 4.0.3
                    


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.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 Stratara.Testing --version 4.0.3
                    


                    

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


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Testing&version=4.0.3
                    


                            Install as a Cake Tool

Stratara.Testing

Derived. The behaviour described here is specified under openspec/specs/. Those specifications are the source; this page explains and illustrates them.

Test doubles and assertion helpers for applications built on the Stratara framework. Unit-test your event-sourced aggregates, encryption, messaging, and session-aware code without spinning up Postgres or RabbitMQ testcontainers.

Contents

  • AggregateTestHarness<T> / Aggregate.Rehydrate<T>(...) — given/when/then rehydration of an aggregate from events, using the same Apply(...) dispatch as production. Throws on an unmapped event so a forgotten overload fails the test (opt out with IgnoringUnmappedEvents()).
  • InMemoryKeyStore — an IKeyStore that mints random 256-bit DEKs per scope and supports rotation / revocation / scope-erasure, without a master KEK or key file.
  • TestBlobEncryptor.CreateAesGcm() — the real AES-GCM ISecureBlobEncryptor over an InMemoryKeyStore, so blob round-trips exercise production encryption.
  • InMemoryMessageBus — an IMessageBus with synchronous in-process dispatch and a Published list for assertions.
  • TestSessionContext / TestSessionContextProvider — preset Actor/Subject SessionContext values and an ISessionContextProvider double.
  • InMemoryTenantMembershipStore — an ITenantMembershipStore mirroring the EF store's contract semantics, including the membership-guarded active-tenant selection and the erasure sweeps.
  • InMemorySettingStore — an ISettingStore with exact-scope reads/writes, so the scoped-settings fallback chain can be exercised without a database.
  • InMemoryApiKeyStore — an IApiKeyStore mirroring the EF store's contract semantics: issuance, idempotent import of a caller-supplied key, fail-closed validation, revocation, erasure sweeps, and machine keys materialized into a membership store you can share and inspect.
  • TestTenants.Of("acme") — stable, deterministic tenant/user ids derived from readable slugs.
  • TestEvent.Create(payload, ...) — wrap an event payload in IEvent<T> with realistic metadata.
  • ProjectionTester.HandleAsync(projection, event) — invoke a projection's (private) HandleAsync handler directly, so you can unit-test it against mocked repositories.

Example

var account = AggregateTestHarness<Account>
    .Given(new AccountOpened(id, "Ada", 100m))
    .And(new AmountWithdrawn(id, 30m))
    .Build();

Assert.Equal(70m, account.Balance);

Dependencies

  • Stratara.Abstractions, Stratara.Contracts, Stratara.Shared, Stratara.Security
  • Microsoft.Extensions.DependencyInjection

Reference it from your test projects only (<PackageReference Include="Stratara.Testing" />). It is not meant for production code paths — the InMemoryKeyStore and DummyKeyStore provide no durability or KEK custody.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  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 Stratara.Testing:

Package Downloads
Stratara.Testing.EntityFrameworkCore

Spin up the real Stratara event-sourcing write stack (EventSource, aggregation, snapshots, the EF Core write store) against a shared in-memory SQLite database in one call — production code paths, no Postgres, no Docker. Builds on Stratara.Testing's in-memory doubles.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.0.3 45 9/3/2026
4.0.2 87 9/3/2026
4.0.1 50 9/2/2026
4.0.0 202 8/31/2026
4.0.0-preview.1 46 8/31/2026
3.4.0 254 8/28/2026
3.3.0 257 8/25/2026
3.2.3 116 8/22/2026
3.2.2 485 8/14/2026
3.2.1 358 8/2/2026
3.2.0 123 7/18/2026
3.1.7 128 7/1/2026
3.1.6 133 6/22/2026
3.1.5 131 6/22/2026
3.1.4 123 6/15/2026
3.1.3 133 6/10/2026
3.1.2 138 6/5/2026

Three fixes to the same complaint: a host composed exactly as the documentation describes did not
start. Each one was a registration the composites assumed somebody else had made — a tracer, a unit
of work, a Redis connection — and each is now made by the registration that needs it. Nothing that
already worked changes: every fix defers to a registration the host makes itself, in either order,
so the lines a working host added to get past these gaps can simply be deleted. Additive on every
published surface.

### Fixed

- **A host without Redis starts and dispatches.** Every composite that carries a dispatcher
 registered the projection-replay state, and its only implementation took a Redis connection that
 no composite registers, so a host composed as documented failed at its first dispatch unless it
 also ran Redis and called `AddCaching()`. `AddProjectionReplayState()` now chooses at first
 resolution: with a registered `IConnectionMultiplexer` the Redis-backed state as before, without
 one an in-process state with the same lease semantics — and a warning, once at start-up
 (`104_012`), that replay coordination is confined to that process, so a replay requested there
 suppresses publication there only. A deployment whose replay must reach several hosts registers
 the shared connection, in either order. Redis-backed hosts observe no change.
- **Registering a store context now registers its unit of work.**
 `AddNpgsqlWriteDbContextFactory<T>()` registered the context factory, the context and the default
 connection resolver but not the `IWriteUnitOfWork` that the event source, the outbox dispatcher and
 the command worker take from the container — and nothing else in the published packages did, so a
 host composed exactly as documented failed at its first command with a dependency-injection error.
 The write registration now try-adds a scoped `IWriteUnitOfWork` over its context, and
 `AddNpgsqlReadDbContextFactory<T>()` try-adds `IProjectionsUnitOfWork` and `IReadUnitOfWork`
 likewise. A unit of work the host registers itself, before or after, is still the one used; a
 hand-written registration can simply be deleted.
- **`AddMediator()` no longer requires the host to register an OpenTelemetry `Tracer`.** The
 mediator traces every dispatch and obtained its tracer from the host, but nothing registered one,
 so a host that called `AddMediator()` and nothing else failed at the first resolve of `IMediator`.
 `AddMediator()` now registers a fallback that emits the dispatch spans from the framework's
 `Stratara.Application` activity source — a host that subscribes to framework telemetry sees them,
 a host that subscribes to nothing pays for nothing. A `Tracer` the host registers, before or after
 `AddMediator()`, is still the one used, so no existing host changes behaviour; the registration
 line can simply be deleted. The samples, the README and the package README no longer carry it.