Stratara.Testing.EntityFrameworkCore
4.4.8
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Testing.EntityFrameworkCore --version 4.4.8
NuGet\Install-Package Stratara.Testing.EntityFrameworkCore -Version 4.4.8
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" Version="4.4.8" />
<PackageVersion Include="Stratara.Testing.EntityFrameworkCore" Version="4.4.8" />
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" />
paket add Stratara.Testing.EntityFrameworkCore --version 4.4.8
#r "nuget: Stratara.Testing.EntityFrameworkCore, 4.4.8"
#:package Stratara.Testing.EntityFrameworkCore@4.4.8
#addin nuget:?package=Stratara.Testing.EntityFrameworkCore&version=4.4.8
#tool nuget:?package=Stratara.Testing.EntityFrameworkCore&version=4.4.8
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.13)
- Microsoft.Extensions.DependencyInjection (>= 10.0.13)
- Stratara.Abstractions (>= 4.4.8)
- Stratara.Contracts (>= 4.4.8)
- Stratara.EventSourcing.EntityFrameworkCore (>= 4.4.8)
- Stratara.Infrastructure (>= 4.4.8)
- Stratara.Shared (>= 4.4.8)
- Stratara.Testing (>= 4.4.8)
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.7.0 | 277 | 10/30/2026 |
| 4.6.1 | 91 | 10/29/2026 |
| 4.6.0 | 121 | 10/28/2026 |
| 4.5.0 | 222 | 10/28/2026 |
| 4.4.10 | 176 | 10/26/2026 |
| 4.4.9 | 113 | 10/26/2026 |
| 4.4.8 | 213 | 10/24/2026 |
| 4.4.7 | 114 | 10/23/2026 |
| 4.4.6 | 166 | 10/22/2026 |
| 4.4.5 | 118 | 10/14/2026 |
| 4.4.4 | 103 | 10/10/2026 |
| 4.4.3 | 110 | 10/10/2026 |
| 4.4.2 | 226 | 10/2/2026 |
| 4.4.1 | 125 | 9/29/2026 |
| 4.4.0 | 114 | 9/27/2026 |
| 4.3.1 | 115 | 9/25/2026 |
| 4.3.0 | 146 | 9/23/2026 |
| 4.2.0 | 179 | 9/18/2026 |
| 4.1.1 | 109 | 9/16/2026 |
| 4.1.0 | 114 | 9/16/2026 |
A fix for hosts on the Orleans execution model. A store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.
### Fixed
- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
longer than the response timeout on another silo waited for that run in its own start. The start then failed
with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
work rather than a busy one.