Stratara.Testing.EntityFrameworkCore
4.4.4
Prefix Reserved
dotnet add package Stratara.Testing.EntityFrameworkCore --version 4.4.4
NuGet\Install-Package Stratara.Testing.EntityFrameworkCore -Version 4.4.4
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" Version="4.4.4" />
<PackageVersion Include="Stratara.Testing.EntityFrameworkCore" Version="4.4.4" />
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" />
paket add Stratara.Testing.EntityFrameworkCore --version 4.4.4
#r "nuget: Stratara.Testing.EntityFrameworkCore, 4.4.4"
#:package Stratara.Testing.EntityFrameworkCore@4.4.4
#addin nuget:?package=Stratara.Testing.EntityFrameworkCore&version=4.4.4
#tool nuget:?package=Stratara.Testing.EntityFrameworkCore&version=4.4.4
Stratara.Testing.EntityFrameworkCore
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
Spin up the real Stratara event-sourcing write stack — IEventSource, IAggregationService,
snapshots, and the EF Core write store — against a shared in-memory SQLite database, in one
call. You exercise production code paths (real serialization, real version tracking, real unique
constraints) without Postgres or Docker.
Builds on Stratara.Testing: the cross-cutting
dependencies are wired with its in-memory doubles (InMemoryKeyStore, TestSessionContextProvider).
Why not a hand-rolled in-memory IEventSource?
Because a bespoke fake would drift from production (subject resolution, concurrency detection,
outbox dispatch, snapshots). This package runs the genuine EventSource on SQLite instead, so your
tests verify the real behavior.
Example
await using var host = EventStoreTestHost.Create(s =>
s.AddAggregatesFromAssemblyContaining<Account>());
await host.ExecuteAsync(async events =>
{
await events.CreateAsync<Account>(id, new AccountOpened(id, tenantId, "Ada", 100m));
await events.AppendAsync<Account>(id, new AmountWithdrawn(30m));
await events.SaveChangesAsync();
});
var account = await host.AggregateAsync<Account>(id);
Assert.Equal(70m, account!.Balance);
Assert.Single(host.Outbox.Bundles); // the SaveChanges emitted one bundle
Contents
EventStoreTestHost— owns a shared open SQLite connection + a configured service provider; exposesExecuteAsync(IEventSource),AggregateAsync<T>(streamId), the presetSession, and the recordingOutbox.IAsyncDisposable.AddStrataraTestingEventStore<TWriteDbContext>(connection, tenantId)— the lower-level DI extension if you compose the provider yourself. The overload that takes a connection string opens a connection per context to a shared-cache in-memory database — for a store used from several threads, such as a silo's — and applies anAction<DbContextOptionsBuilder>after the provider, for an interceptor.StrataraTestWriteDbContext— a ready-made concrete write context (no subclass boilerplate).RecordingEventBundleOutboxDispatcher— captures emitted bundles for assertions.
Notes
- The SQLite connection is
:memory:and shared across every DbContext the unit of work mints — it must stay open for the host's lifetime (the host manages this; dispose it when done). - Register your aggregates (
AddAggregatesFromAssemblyContaining<T>()) so event payload types deserialize on rehydration.
Dependencies
Stratara.Testing,Stratara.Infrastructure,Stratara.EventSourcing.EntityFrameworkCore,Stratara.Shared,Stratara.Abstractions,Stratara.ContractsMicrosoft.EntityFrameworkCore.Sqlite
Reference it from test projects only.
| 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.EntityFrameworkCore.Sqlite (>= 10.0.11)
- Microsoft.Extensions.DependencyInjection (>= 10.0.11)
- Stratara.Abstractions (>= 4.4.4)
- Stratara.Contracts (>= 4.4.4)
- Stratara.EventSourcing.EntityFrameworkCore (>= 4.4.4)
- Stratara.Infrastructure (>= 4.4.4)
- Stratara.Shared (>= 4.4.4)
- Stratara.Testing (>= 4.4.4)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Stratara.Testing.EntityFrameworkCore:
| Package | Downloads |
|---|---|
|
Stratara.Testing.Orleans
Run the Stratara Orleans execution model in a test's own process — one silo with in-memory reminders and grain directory, the real write stack, commit-order reader and checkpoint store on in-memory SQLite, and every period shortened to seconds. Register handlers, projections, sagas and timers with the production calls; no cluster, broker or database server. Builds on Stratara.Testing.EntityFrameworkCore. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.4.4 | 40 | 10/10/2026 |
| 4.4.3 | 44 | 10/10/2026 |
| 4.4.2 | 142 | 10/2/2026 |
| 4.4.1 | 113 | 9/29/2026 |
| 4.4.0 | 101 | 9/27/2026 |
| 4.3.1 | 107 | 9/25/2026 |
| 4.3.0 | 137 | 9/23/2026 |
| 4.2.0 | 166 | 9/18/2026 |
| 4.1.1 | 100 | 9/16/2026 |
| 4.1.0 | 105 | 9/16/2026 |
| 4.0.4 | 158 | 9/14/2026 |
| 4.0.3 | 127 | 9/3/2026 |
| 4.0.2 | 107 | 9/3/2026 |
| 4.0.1 | 104 | 9/2/2026 |
| 4.0.0 | 109 | 8/31/2026 |
| 4.0.0-preview.1 | 79 | 8/31/2026 |
| 3.4.0 | 101 | 8/28/2026 |
| 3.3.0 | 114 | 8/25/2026 |
| 3.2.3 | 115 | 8/22/2026 |
| 3.2.2 | 120 | 8/14/2026 |
A one-fix release. On the Redis-backed replay state, a host could report a replay still active after it had ended
it, holding publication back for up to one refresh interval. Nothing else changes; no configuration or migration is
needed.
### Fixed
- **A host no longer reports a replay active after it ended the replay itself.** On the Redis-backed replay state, a
refresh that had read the marking just before the host's own deactivation could compare its generation before the
deactivation and write the field after it, leaving `IsReplayActive` true — and publication held back — until the
next refresh (`ProjectionReplay:RefreshSeconds`, default 5). The comparison and the write are now one step with the
transition. Present since 4.4.2.