Stratara.Testing.EntityFrameworkCore 4.4.9

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.EntityFrameworkCore --version 4.4.9
                    


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" />
                    


                            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.EntityFrameworkCore --version 4.4.9
                    


                    

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


                            Install as a Cake Addin
                        

                    

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


                            Install as a Cake Tool

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; exposes ExecuteAsync(IEventSource), AggregateAsync<T>(streamId), the preset Session, and the recording Outbox. 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 an Action<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.Contracts
  • Microsoft.EntityFrameworkCore.Sqlite

Reference it from test projects only.

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.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
Loading failed

A fix for hosts on the Orleans execution model. A host that removed or renamed a projection no longer has that
projection's store readers come back on every start and fail each entry; they retire once, as a saga's readers do. A
retired store reader now logs its retirement once instead of three times, and leaves no reminder error behind. No
API change, no schema change and no migration.

### Fixed

- **A reader of a removed projection retires.** On the Orleans execution model, a host that removed or renamed a
 projection kept the keep-alive reminders of its store readers. On every start of the silo they brought the readers
 back, and each one read the next entry of its partition, failed it because no projection of its name was
 registered, and tried again on the next tick, without end — a warning per partition and entry. Such a reader now
 retires the first time it is brought back, as a saga's reader already did: it unregisters its keep-alive, logs
 `117_136` `UnregisteredProjectionReaderRetired` (Information) once, reads nothing and deactivates. Its checkpoints
 stay, so a projection registered again resumes where it stopped; *Operate the Orleans execution model* says how to
 delete them. In a rolling deployment that adds a projection, a reader that lands on a silo of the earlier version
 refuses a rebuild's or a replay's pause, which then fails naming it, and a wait counts its partition as behind.
- **A retired store reader logs its retirement once.** A reader that retired as it was activated — of a partition
 beyond a lowered partition count, or of a saga the silo no longer registers — deactivated before it answered the
 call that activated it. Orleans forwarded that call to a new activation, which retired again, so the retirement was
 logged three times per reader and the keep-alive tick ended in `Could not deliver reminder tick` at Error. The
 reader now answers the call first and deactivates after it.