Stratara.Testing.EntityFrameworkCore
3.1.5
See the version list below for details.
dotnet add package Stratara.Testing.EntityFrameworkCore --version 3.1.5
NuGet\Install-Package Stratara.Testing.EntityFrameworkCore -Version 3.1.5
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" Version="3.1.5" />
<PackageVersion Include="Stratara.Testing.EntityFrameworkCore" Version="3.1.5" />
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" />
paket add Stratara.Testing.EntityFrameworkCore --version 3.1.5
#r "nuget: Stratara.Testing.EntityFrameworkCore, 3.1.5"
#:package Stratara.Testing.EntityFrameworkCore@3.1.5
#addin nuget:?package=Stratara.Testing.EntityFrameworkCore&version=3.1.5
#tool nuget:?package=Stratara.Testing.EntityFrameworkCore&version=3.1.5
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; 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.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.8)
- Microsoft.Extensions.DependencyInjection (>= 10.0.8)
- Stratara.Abstractions (>= 3.1.5)
- Stratara.Contracts (>= 3.1.5)
- Stratara.EventSourcing.EntityFrameworkCore (>= 3.1.5)
- Stratara.Infrastructure (>= 3.1.5)
- Stratara.Shared (>= 3.1.5)
- Stratara.Testing (>= 3.1.5)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- **Configurable snapshot strategy** (`Stratara.Abstractions`, `Stratara.Infrastructure`) — the
snapshot cadence is no longer hard-coded. A new `Stratara.Abstractions.EventSourcing.ISnapshotStrategy`
decides, per stream, whether the event-sourcing runtime should write a snapshot:
`bool ShouldSnapshot(Type aggregateType, long currentVersion, long lastSnapshotVersion)`.
`AddEventSourcing()` registers the default `VersionThresholdSnapshotStrategy` (snapshot every 50
versions — identical to the previous behaviour) via `TryAddSingleton`, so existing consumers see no
change. To take over the policy, register your own singleton `ISnapshotStrategy` (it overrides the
default whether registered before or after `AddEventSourcing()`): vary the threshold per aggregate
type, construct `new VersionThresholdSnapshotStrategy(threshold)` for a different uniform cadence, or
register `NoSnapshotStrategy` to disable snapshotting entirely. This replaces the previously
hard-coded `UseSnapshots`/`SnapshotRange` constants in the default snapshot service, which were not
actually configurable despite the documentation implying they were.
- **`AddDomainEventTypesFromAssemblyContaining<T>()`** (`Stratara.Abstractions`) — registers *only* the
domain event types consumed by an assembly's aggregate `Apply(TEvent)` methods in the trusted-type
resolver, without registering the aggregate types themselves and without pulling any projection / saga
/ command-handler classes into DI. Use it in a host that only needs to deserialize event payloads off
the message bus or event stream — typically a dedicated projection or saga worker — but must not wire
the handler classes (and their runtime dependencies) that `AddProjectionsFromAssemblyContaining<T>`
would register. Complements the existing `AddAggregatesFromAssemblyContaining<T>` (which additionally
registers the aggregate types) and `AddTrustedType<T>` (single type).