Stratara.Testing
4.4.10
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Testing --version 4.4.10
NuGet\Install-Package Stratara.Testing -Version 4.4.10
<PackageReference Include="Stratara.Testing" Version="4.4.10" />
<PackageVersion Include="Stratara.Testing" Version="4.4.10" />
<PackageReference Include="Stratara.Testing" />
paket add Stratara.Testing --version 4.4.10
#r "nuget: Stratara.Testing, 4.4.10"
#:package Stratara.Testing@4.4.10
#addin nuget:?package=Stratara.Testing&version=4.4.10
#tool nuget:?package=Stratara.Testing&version=4.4.10
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 sameApply(...)dispatch as production. Throws on an unmapped event so a forgotten overload fails the test (opt out withIgnoringUnmappedEvents()).InMemoryKeyStore— anIKeyStorethat 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-GCMISecureBlobEncryptorover anInMemoryKeyStore, so blob round-trips exercise production encryption.InMemoryMessageBus— anIMessageBuswith synchronous in-process dispatch and aPublishedlist for assertions.TestSessionContext/TestSessionContextProvider— preset Actor/SubjectSessionContextvalues and anISessionContextProviderdouble.InMemoryTenantMembershipStore— anITenantMembershipStoremirroring the EF store's contract semantics, including the membership-guarded active-tenant selection and the erasure sweeps.InMemorySettingStore— anISettingStorewith exact-scope reads/writes, so the scoped-settings fallback chain can be exercised without a database.InMemoryApiKeyStore— anIApiKeyStoremirroring 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 inIEvent<T>with realistic metadata.ProjectionTester.HandleAsync(projection, event)— invoke a projection's (private)HandleAsynchandler 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.SecurityMicrosoft.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 | Versions 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. |
-
net10.0
- Microsoft.Extensions.DependencyInjection (>= 10.0.13)
- Stratara.Abstractions (>= 4.4.10)
- Stratara.Contracts (>= 4.4.10)
- Stratara.Security (>= 4.4.10)
- Stratara.Shared (>= 4.4.10)
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.8.0 | 139 | 11/6/2026 |
| 4.7.1 | 117 | 11/5/2026 |
| 4.7.0 | 505 | 10/30/2026 |
| 4.6.1 | 124 | 10/29/2026 |
| 4.6.0 | 184 | 10/28/2026 |
| 4.5.0 | 252 | 10/28/2026 |
| 4.4.10 | 195 | 10/26/2026 |
| 4.4.9 | 128 | 10/26/2026 |
| 4.4.8 | 231 | 10/24/2026 |
| 4.4.7 | 133 | 10/23/2026 |
| 4.4.6 | 207 | 10/22/2026 |
| 4.4.5 | 497 | 10/14/2026 |
| 4.4.4 | 212 | 10/10/2026 |
| 4.4.3 | 123 | 10/10/2026 |
| 4.4.2 | 336 | 10/2/2026 |
| 4.4.1 | 194 | 9/29/2026 |
| 4.4.0 | 145 | 9/27/2026 |
| 4.3.1 | 218 | 9/25/2026 |
| 4.3.0 | 289 | 9/23/2026 |
| 4.2.0 | 187 | 9/18/2026 |
A release for hosts on the Orleans execution model. A durable timer now answers its tick while its handler runs, so a
long handler leaves no reminder error in the silo's log, and a timer that fails is logged by the framework with its
owner and purpose. A commit no longer constructs every registered projection to learn which store readers to wake. No
API change, no schema change and no migration.
### Changed
- **A commit no longer constructs every projection.** On the Orleans execution model, every command that committed
facts constructed each registered projection, with its dependencies, only to learn the names of the store readers to
wake. The names are now worked out once per silo, and the wait for a projection, the rebuild and the full replay's
checkpoint reset use the same list. A rebuild of a name that is not registered is refused before any reader is
paused, with the same message as before.
### Fixed
- **A durable timer answers its tick while its handler runs.** On the Orleans execution model, a durable timer's
reminder call stayed open until its handler returned, so a handler longer than the runtime's response timeout made
Orleans log `Could not deliver reminder tick` at Error for every tick it outlasted. The tick is now answered at once
and the handler runs in a call that carries no response timeout. The timer still fires once per due time, a tick
during its handler still does nothing, and a handler stopped with its silo still fires again on the next one.
- **A failing timer is logged.** A durable timer whose handler threw — or whose owner check or unregistration
failed — was visible only as Orleans' reminder error line. It is now logged as `117_137` `TimerFiringFailed` (Error)
with the owner, the purpose and the exception, and the timer fires again after its retry period as before.