Stratara.Testing.EntityFrameworkCore 3.1.3

.NET 10.0

dotnet add package Stratara.Testing.EntityFrameworkCore --version 3.1.3

NuGet\Install-Package Stratara.Testing.EntityFrameworkCore -Version 3.1.3

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.1.3" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="Stratara.Testing.EntityFrameworkCore" Version="3.1.3" />
                    

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

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: Stratara.Testing.EntityFrameworkCore, 3.1.3"

#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.1.3

#: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.1.3
                    

                            Install as a Cake Addin

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

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

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

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.

net10.0
- Microsoft.EntityFrameworkCore.Sqlite (>= 10.0.8)
- Microsoft.Extensions.DependencyInjection (>= 10.0.8)
- Stratara.Abstractions (>= 3.1.3)
- Stratara.Contracts (>= 3.1.3)
- Stratara.EventSourcing.EntityFrameworkCore (>= 3.1.3)
- Stratara.Infrastructure (>= 3.1.3)
- Stratara.Shared (>= 3.1.3)
- Stratara.Testing (>= 3.1.3)

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.1.3	34	6/10/2026
3.1.2	104	6/5/2026

### Added

- **Mediator tenant-isolation behavior** (`Stratara.Mediator`) — `AddStrataraTenantIsolation()`
registers a pipeline behavior that enforces tenant isolation at the mediator entrance, before the
handler runs, for any request that opts in via the new `ITenantScopedRequest` marker
(`Stratara.Abstractions.Multitenancy`). The behavior compares the request's `TenantId` (data owner)
against the ambient session's data-owner tenant and rejects a mismatch with the new
`TenantAccessDeniedException` (translated to HTTP 403 on ASP.NET hosts). `TenantIsolationMode.Default`
enforces only the subject match (privileged cross-tenant operations pass when the endpoint promoted
the session subject to the target); `TenantIsolationMode.Strict` additionally routes every
cross-tenant operation through the new `ICrossTenantAuthorizer`, whose shipped default denies all
cross-tenant access until a consumer registers its own authorizer. Complements the existing
database-side `ApplyGlobalTenantQueryFilters` with a command-/query-entrance guard. New log-event
IDs `114_101`/`114_102`/`114_003` in `Stratara.Diagnostics`.
- **`Stratara.Abstractions.Persistence.ConcurrencyConflictException`** — provider-agnostic
wrapper for an optimistic-concurrency conflict detected during commit. Allows framework-level
code in `Stratara.Projections` (and any consumer outside the `EntityFrameworkCore` package) to
react to concurrency without taking an EF Core dependency. EF Core's `DbUpdateConcurrencyException`
(and provider equivalents) flow through this type.

### Changed

- **`EfTransaction.SaveChangesAsync`** (in `Stratara.EventSourcing.EntityFrameworkCore`) now
wraps `DbUpdateConcurrencyException` thrown by EF Core in the new
`ConcurrencyConflictException`. PostgreSQL unique-violation paths remain on `DbUpdateException`
(different semantics — duplicate-key on insert vs. stale-row on update/delete).
- **`EventSource.SaveChangesAsync`** (write-side append flow) extends its concurrency-handling
catch to the new exception type so the existing append-conflict recovery path keeps working
after the wrap. Behaviour for both EF concurrency conflicts and PostgreSQL unique violations
is unchanged.

### Fixed

- **`TenantProjection` no longer aborts the event bundle on a parallel delete race.** The two
delete handlers (`TenantDeleted`, `CustomerTenantsDeleted`) now swallow
`ConcurrencyConflictException` silently — a missing row is the desired end-state of a delete.
Before this fix, a consumer-side customer-delete cascade saga that emits both
`CustomerTenantsDeleted` and a follow-up `TenantDeleted` for the same tenants would race the
two parallel projection bundles on the same `TenantView` row; the loser threw
`DbUpdateConcurrencyException` out of `SaveChangesAsync`, which propagated through
`ProjectionWorker` and caused `RabbitMqBus` to roll back the entire bundle — including
sibling projections that had already committed. Update handlers (rename / activate /
deactivate / locale / customer-assigned) keep their current behaviour: a concurrency failure
there is a real race that propagates.