Stratara.Testing 4.0.2

Prefix Reserved
.NET 10.0 This package targets .NET 10.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 Stratara.Testing --version 4.0.2
                    


                    

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


                            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.2
                    


                    

                
#r "nuget: Stratara.Testing, 4.0.2"
#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.2
#: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.2
                    


                            Install as a Cake Addin
                        

                    

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


                            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 54 9/3/2026
4.0.2 87 9/3/2026
4.0.1 51 9/2/2026
4.0.0 221 8/31/2026
4.0.0-preview.1 46 8/31/2026
3.4.0 263 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 124 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

Two operational fixes, both found while a consumer rolled out bus-envelope signing and reasoned
about rebuilding its read models: a projection replay now survives a passing failure, and an
integrity failure says whether the signature was absent or wrong. Additive on every published
surface.

### Added

- **A projection replay retries a failing batch before it gives up.** Each batch — the read from
 the event store and the application of its entries — now runs under a new named policy,
 `ResilienceNames.ProjectionReplayBatch`: five attempts in all, exponential backoff from one second
 with jitter between them, any exception except cancellation. A read-store timeout or a
 dropped connection mid-rebuild no longer ends the replay; a failure that persists through every
 attempt ends it exactly as before, with the same failure record. A retried batch is applied
 again from its first entry in a fresh scope, which relies on the guarantee projections already
 give under at-least-once delivery: a second application converges (see *Write handlers that
 converge rather than accumulate* in the projection guide). Each failed attempt logs a new
 warning, `104_011`. `AddResiliencePipelines` registers six policies rather than five. Nothing
 about truncation, ordering, progress, the failure record or the lease changes.

### Changed

- **An integrity failure now says whether the signature was absent or wrong, and the existing
 warning and error ids fire only for a signature that is present and does not verify.** An
 unsigned envelope — what every not-yet-restarted publisher emits during a `Permissive` roll —
 was logged as *"signature mismatch"* under the same id as a key mismatch or tampering, so an
 operator could not tell a rolling restart from an attack without correlating host start times.
 Four new event ids carry the unsigned case: `105_004` (command, permissive), `111_004` (event
 bundle, permissive), `105_105` (command, strict) and `111_105` (event bundle, strict). The
 existing `105_003`, `111_003`, `105_104` and `111_104` keep their numbers and their level but
 now mean a present signature that did not verify; an alert keyed on one of them goes quiet
 during a roll instead of firing for every unsigned message. Strict-mode rejections name the
 case in their exception message. `BusEnvelopeIntegrityVerifier.Verify` gains an overload with
 `out BusEnvelopeIntegrityFailure` (`None`, `Absent`, `Invalid`); the existing overload and the
 `BusEnvelopeIntegrityResult` values are unchanged. An absent signature no longer reaches the
 signer, which already answered `false` for it.