Stratara.Testing.EntityFrameworkCore
3.2.2
dotnet add package Stratara.Testing.EntityFrameworkCore --version 3.2.2
NuGet\Install-Package Stratara.Testing.EntityFrameworkCore -Version 3.2.2
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" Version="3.2.2" />
<PackageVersion Include="Stratara.Testing.EntityFrameworkCore" Version="3.2.2" />
<PackageReference Include="Stratara.Testing.EntityFrameworkCore" />
paket add Stratara.Testing.EntityFrameworkCore --version 3.2.2
#r "nuget: Stratara.Testing.EntityFrameworkCore, 3.2.2"
#:package Stratara.Testing.EntityFrameworkCore@3.2.2
#addin nuget:?package=Stratara.Testing.EntityFrameworkCore&version=3.2.2
#tool nuget:?package=Stratara.Testing.EntityFrameworkCore&version=3.2.2
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.2.2)
- Stratara.Contracts (>= 3.2.2)
- Stratara.EventSourcing.EntityFrameworkCore (>= 3.2.2)
- Stratara.Infrastructure (>= 3.2.2)
- Stratara.Shared (>= 3.2.2)
- Stratara.Testing (>= 3.2.2)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
API keys can now be bootstrapped. Issuance always generated the key itself, which does not fit the
setups where server and caller have to share a key *before* either starts — container orchestration,
CI provisioning, self-hosted bundles, end-to-end test hosts. This release adds an import path for a
key the caller already holds, plus the canonical key format as public API so callers generate values
instead of inventing them.
### Added
- **`IApiKeyStore.ImportAsync` — store a machine key whose raw value the caller already holds.**
Issuance generates the key itself, which is the wrong shape when server and caller must share it
*before* either boots: container orchestration, CI provisioning, self-hosted bundles, end-to-end
test hosts. Without this path, consumers bypassed the store and reimplemented its internals (the
digest format and the machine-key membership row) — a copy that keeps compiling after the store
changes and fails as a runtime 401. Import is idempotent, so it can run unconditionally on every
boot: a value that is already stored returns the existing descriptor and the stored key is never
mutated, so a changed configuration cannot escalate a key's roles or extend its expiry unnoticed.
Revoked, expired, and foreign-tenant values are rejected rather than silently adopted, and
concurrent replicas racing the same first import converge on one key. Machine keys only —
`ApiKeyImportRequest` carries no `UserId`.
- **`ApiKeyFormat` (`Stratara.Abstractions.ApiKeys`) — the canonical raw-key format as public API.**
`CreateRawKey()` generates `stk_` plus the Base64Url encoding of 32 CSPRNG bytes; `IsWellFormed()`
checks that shape. `ImportAsync` accepts only well-formed values: the store keeps its stored
digest unsalted because a generated key carries 256 bits of entropy, and a hand-picked value would
quietly invalidate that. Generate keys out of band with `CreateRawKey()` and keep them in a secret
store — the type lives in the abstractions package so host-builder and orchestration projects can
reach it without referencing the storage implementation.
- **`InMemoryApiKeyStore` (`Stratara.Testing`) — the drop-in double for the API-key store**,
mirroring issuance, import, fail-closed validation, revocation, and the erasure sweeps, and
materializing machine keys into a membership store you can share and inspect.
### Changed
- **API-key lifecycle events are now logged** (`Stratara.Diagnostics` event-ID range 116_000):
import, idempotent repeat, and a repeat that supplied different parameters. Key ids and tenant
ids only — never the raw key or its digest.
- **For implementers of `IApiKeyStore`:** the interface gained `ImportAsync`. Custom implementations
need the new member; callers are unaffected.