Stratara.Testing.EntityFrameworkCore 4.6.0

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


                    

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


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


                    

                
#r "nuget: Stratara.Testing.EntityFrameworkCore, 4.6.0"
#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.6.0
#: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.6.0
                    


                            Install as a Cake Addin
                        

                    

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


                            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

An erasure shreds every key that names the subject, and nothing stopped the next encryption for that subject
from creating a new one: a key store asked for a scope it does not hold creates a first version. A job, a request
in flight or a second process that encrypted for an erased subject afterwards got a fresh key, and what it wrote
stayed readable for good. The key store now records an erased subject and refuses to create a key for it again.

### Added

- **`IKeyStore.MarkSubjectErasedAsync(KeySubject)`** records that a tenant or user has been erased. It has a
 default implementation that throws `NotSupportedException`, so an existing key store still compiles.
- **`KeySubject`** names the tenant or user, and `KeySubject.Covers(KeyScope)` states which keys belong to its
 erasure: for a tenant, a key of any level that names it; for a user, a user-level key that names it.
- **`KeyScopeErasedException`** (an `InvalidOperationException`) is what a key store throws for such a scope. It
 carries the refused `Scope`.

### Changed

- **An encryption for an erased subject fails.** After a subject's erasure, `GetOrCreateCurrentKeyAsync` and
 `RotateAsync` throw `KeyScopeErasedException` for every scope the subject covers, whether or not it ever held a
 key, and create nothing. The blob encryptor, the encrypting settings store and the field-encrypting serializer
 pass it through. Code that erased a subject and then wrote encrypted data for it again now sees the exception;
 the mark is permanent and cannot be lifted. Revoking every version of a scope is not an erasure and marks nothing.
- **`ISubjectEraser` marks the subject before it sweeps any plane**, so an encryption racing the erasure
 either creates its key first, and that key is shredded with the rest, or is refused. A key store that cannot mark
 a subject leaves the erasure as before and logs `SubjectNotMarkable` (112009).
- **The file-backed key store writes format version 2**, which holds the marks, and refuses to open a file in a
 newer format than it knows. `InMemoryKeyStore` refuses an erased subject as the file store does; `DummyKeyStore`
 refuses to mark one, as it refuses every erasure operation.

**Upgrading:**
- **Upgrade every process that shares a key store file in one step.** A process on an earlier release reads a
 version-2 file, ignores the marks, creates keys for an erased subject and drops the marks the next time it writes
 the file. A version-1 file needs no migration. Rolling back is possible but loses the marks on the first write.
- **Map `KeyScopeErasedException` to your answer for data that is gone**, if a request can reach an encryption for
 a subject after its erasure.
- **A key store of your own implements `MarkSubjectErasedAsync`**, refusing in `GetOrCreateCurrentKeyAsync` and
 `RotateAsync` every scope a marked subject `Covers`. Without it the erasure warns and the gap stays open.