Stratara.Testing.Orleans
4.5.0
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Testing.Orleans --version 4.5.0
NuGet\Install-Package Stratara.Testing.Orleans -Version 4.5.0
<PackageReference Include="Stratara.Testing.Orleans" Version="4.5.0" />
<PackageVersion Include="Stratara.Testing.Orleans" Version="4.5.0" />
<PackageReference Include="Stratara.Testing.Orleans" />
paket add Stratara.Testing.Orleans --version 4.5.0
#r "nuget: Stratara.Testing.Orleans, 4.5.0"
#:package Stratara.Testing.Orleans@4.5.0
#addin nuget:?package=Stratara.Testing.Orleans&version=4.5.0
#tool nuget:?package=Stratara.Testing.Orleans&version=4.5.0
Stratara.Testing.Orleans
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
Run the Orleans execution model in a test's own process. ExecutionModelTestHost starts one
silo clustered with itself, with reminders and the grain directory in memory, and the framework's
real write stack, portable commit-order reader, checkpoint store and intent store on an in-memory
SQLite database. Every period the model keeps as a reminder or a poll is shortened to seconds, so a
projection applies and a timer fires within a test. No cluster, no broker, no database server, no
Docker.
Builds on Stratara.Testing.EntityFrameworkCore.
Why run the real grains?
Because the registration is what a test should prove. Your handlers, projections, sagas, processes
and timer ports are registered with the calls production uses — AddStrataraAggregateGrains,
AddStrataraProjectionGrains, AddStrataraSagaGrains, AddStrataraDurableTimers,
AddStrataraOrleansCommandDispatcher — and run in the same grains, through the same mediator
pipeline, reading the store in commit order from a checkpoint.
Example
await using var host = await ExecutionModelTestHost.CreateAsync(services => services
.AddAggregatesFromAssemblyContaining<Account>()
.AddCommandHandlersFromAssemblyContaining<OpenAccountHandler>()
.AddProjectionsFromAssemblyContaining<BalanceProjection>()
.AddStrataraAggregateGrains()
.AddStrataraProjectionGrains());
await host.DispatchAsync(new OpenAccount(accountId, 100m)); // runs in the account's activation
await host.WaitForReadersAsync(); // every reader is at the store's head
Assert.Equal(100m, balances[accountId]);
Contents
ExecutionModelTestHost—CreateAsync(configure, options),DispatchAsync,WaitForReadersAsync,Timers,SeedAtHeadAsync,ResetAsync, the presetSessionandServices.IAsyncDisposable.ExecutionModelTestHostOptions— the periods (PollInterval250 ms,ReminderPeriod1 s,IntentGrace2 s,DrainPollingInterval1 s), the partition count (4), the start timeout, andBeforeStart, which runs before the silo starts — where a test appends history and seeds the readers at its head, as a deployment does while no silo runs. A value a test sets through a registration's own settings wins over the host's.StrataraTestReadDbContext— the read context that holds the checkpoints.
Share a host across a test class
Creating a host takes a few seconds. Share one through a class fixture and reset it between tests where one must not see another's state:
public sealed class ExecutionModelFixture : IAsyncLifetime
{
public ExecutionModelTestHost Host { get; private set; } = null!;
public async ValueTask InitializeAsync() =>
Host = await ExecutionModelTestHost.CreateAsync(services => services /* the roles */);
public ValueTask DisposeAsync() => Host.DisposeAsync();
}
ResetAsync runs the execution model's reset port on this host, where the silo keeps running: the timers
and the grain directory's entries go, and every registered reader is put at the store's head. The next
test's facts are applied, the last test's are not applied a second time, and WaitForReadersAsync returns
at once. The read models themselves are not emptied — empty or rebuild them in the fixture where a test
needs them clean.
Where the host stops
- One silo. Membership, reminders and the directory are in memory and not shared. What happens across silos — a kill, a role split, a takeover — is an integration test against real infrastructure.
- Test projects only. Referencing the package from a project that is not a test project fails
the build with
STRATARA1001;StrataraAllowTestSupportOutsideTests=trueopts out, as the sample does.CreateAsyncrefuses to run whereDOTNET_ENVIRONMENTorASPNETCORE_ENVIRONMENTstates an environment other thanDevelopment.
Dependencies
Stratara.Orleans,Stratara.Orleans.EntityFrameworkCore,Stratara.Testing.EntityFrameworkCoreMicrosoft.Orleans.Server,Microsoft.Extensions.Hosting
| 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.Extensions.Hosting (>= 10.0.13)
- Microsoft.Orleans.Server (>= 10.3.1 && < 11.0.0)
- Stratara.Orleans (>= 4.5.0)
- Stratara.Orleans.EntityFrameworkCore (>= 4.5.0)
- Stratara.Testing.EntityFrameworkCore (>= 4.5.0)
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 |
|---|---|---|
| 4.8.0 | 126 | 11/6/2026 |
| 4.7.1 | 114 | 11/5/2026 |
| 4.7.0 | 358 | 10/30/2026 |
| 4.6.1 | 105 | 10/29/2026 |
| 4.6.0 | 141 | 10/28/2026 |
| 4.5.0 | 222 | 10/28/2026 |
| 4.4.10 | 173 | 10/26/2026 |
| 4.4.9 | 113 | 10/26/2026 |
| 4.4.8 | 212 | 10/24/2026 |
| 4.4.7 | 112 | 10/23/2026 |
| 4.4.6 | 162 | 10/22/2026 |
| 4.4.5 | 99 | 10/14/2026 |
| 4.4.4 | 108 | 10/10/2026 |
| 4.4.3 | 119 | 10/10/2026 |
| 4.4.2 | 221 | 10/2/2026 |
| 4.4.1 | 119 | 9/29/2026 |
| 4.4.0 | 104 | 9/27/2026 |
| 4.3.1 | 110 | 9/25/2026 |
| 4.3.0 | 142 | 9/23/2026 |
| 4.2.0 | 169 | 9/18/2026 |
A release about reads that cost more the more the store holds. Loading an aggregate read its stream and its
snapshot through every partition of the store, so every command grew slower as the store grew. A write context
that applies `ApplyGlobalEntityConfiguration()` also lost the index on the event stream's sequence number, which
left the hashing worker, reading in sequence order and the store's head without an index. Every read of one stream
is now confined to its partition, and the write model declares the indexes it was missing, whichever key the
context gives the event stream. No public type or member changes, but the write context needs a migration, and a
write context that overrides `ConfigureConventions` without calling `base` is now refused at start-up.
**Upgrading:**
- **If your store holds events written before 3.0.0, check it first.** Releases before 3.0.0 worked out a
stream's partition with another formula, and the store now reads a stream only in the partition its id gives.
The composition guide (*A store written before 3.0.0*) gives a check that needs nothing but the database, and a
repair that moves the rows to their partition without touching the hash chain. A store that 3.0.0 or later wrote
from its start has nothing to check.
- **Generate an EF Core migration for your write context.** It adds up to three indexes and changes no table or
column: `ix_event_stream_entry_sequence_number` (unique, only where the event stream is not keyed by its sequence
number, which `ApplyGlobalEntityConfiguration()` makes it), `ix_event_stream_entry_unhashed_sequence_number`
(the entries whose hash is still null) and `ix_event_chain_anchor_sequence_number`. A host that does not migrate
fails at `Migrate()` on pending model changes, as with any schema addition.
- **If you declared these indexes yourself, remove your declarations first.** Under the same names and
definitions, the migration then leaves them as they are. A `(stream_id, version)` index you added to bridge the
stream reads is no longer needed and can be dropped.
- **On a large store, create the indexes without blocking writes.** The schema section of the composition guide
shows a migration that creates them with `CREATE INDEX CONCURRENTLY`.
- **A context that overrides `ConfigureConventions` calls `base.ConfigureConventions`.** `WriteDbContext<TContext>`
declares the sequence-number indexes there. A write context whose override does not call it is now refused when
its model is built, at start-up and in `dotnet ef` alike, with an `InvalidOperationException` that names the
context, so it never runs or migrates without the indexes. An override that was fine on 4.4 because the
method was empty there needs `base.ConfigureConventions(configurationBuilder);` now.
- **An entry or snapshot written outside the framework has to carry its stream's partition.** The store writes
each one with the partition its stream id gives it, through `BucketCalculator.GetBucketId`, and now reads one
stream only there. A row a host inserted itself under another partition, in a test fixture or an import, is no
longer found by the reads of its stream.
### Fixed
- **Loading an aggregate costs what its stream holds.** The reads of one stream (whether it exists, its first entry,
a range of versions, its current version) and of its snapshot conditioned on the stream id alone. The indexes that
serve them begin with the partition, so PostgreSQL before 18 walked the whole index for each of them, and a
command loads several. They now condition on the partition as well. On 300,000 events, reading a stream of three
went from 2,404 pages to 6.
- **The sequence number stays indexed under `ApplyGlobalEntityConfiguration()`.** That convention keys every entity
by `Id`, the event stream included, which dropped the key the framework had put on the sequence number. The
hashing worker's reads, reading the store in sequence order and the store's head then scanned the whole table on
every pass. The write model now declares a unique index on the sequence number wherever it is not the key.
- **The hashing worker reads only what is still unchained.** An index over the entries whose hash is null lets
each pass read the backlog and not the chained history before it. Its filter names the column your model maps the
hash to.
- **The latest anchor is found by index.** The hash chain's anchors are indexed by sequence number, so finding the
last one no longer sorts every anchor on every pass.