Stratara.Testing.EntityFrameworkCore 3.2.1

dotnet add package Stratara.Testing.EntityFrameworkCore --version 3.2.1
                    
NuGet\Install-Package Stratara.Testing.EntityFrameworkCore -Version 3.2.1
                    
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="3.2.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Testing.EntityFrameworkCore" Version="3.2.1" />
                    
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 3.2.1
                    
#r "nuget: Stratara.Testing.EntityFrameworkCore, 3.2.1"
                    
#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@3.2.1
                    
#: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=3.2.1
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Testing.EntityFrameworkCore&version=3.2.1
                    
Install as a Cake Tool

Stratara.Testing.EntityFrameworkCore

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

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.2.1 0 8/2/2026
3.2.0 94 7/18/2026
3.1.7 106 7/1/2026
3.1.6 101 6/22/2026
3.1.5 109 6/22/2026
3.1.4 113 6/15/2026
3.1.3 112 6/10/2026
3.1.2 123 6/5/2026

### Fixed

- **Snapshot loads are now scoped to the aggregate type.** The snapshot read previously filtered
 only by stream id, so when two aggregate types shared a stream id, rehydrating one type could
 pick up the other type's (higher-versioned) snapshot and deserialize it into the requested type —
 silently returning an aggregate with default/empty fields. Snapshot reads now match the aggregate
 type (version-independently, so an assembly rev-bump does not invalidate existing snapshots), and
 snapshot writes are grouped per `(stream, aggregate type)` so a stream carrying more than one type
 snapshots each type independently. A snapshot of type X may now only ever rehydrate type X.

### Changed

- **`ISnapshotRepository` gained type-scoped read overloads.** `GetAsync(streamId,
 aggregateTypeName, toVersion, ct)` and `GetLatestVersionOrDefaultAsync(streamId,
 aggregateTypeName, ct)` are the correct lookups; the previous type-less overloads are now
 `[Obsolete]` because they can return a foreign aggregate type's snapshot on a shared stream.
 Custom `ISnapshotRepository` implementers should add the new overloads.