Stratara.Testing.Orleans
4.4.9
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Testing.Orleans --version 4.4.9
NuGet\Install-Package Stratara.Testing.Orleans -Version 4.4.9
<PackageReference Include="Stratara.Testing.Orleans" Version="4.4.9" />
<PackageVersion Include="Stratara.Testing.Orleans" Version="4.4.9" />
<PackageReference Include="Stratara.Testing.Orleans" />
paket add Stratara.Testing.Orleans --version 4.4.9
#r "nuget: Stratara.Testing.Orleans, 4.4.9"
#:package Stratara.Testing.Orleans@4.4.9
#addin nuget:?package=Stratara.Testing.Orleans&version=4.4.9
#tool nuget:?package=Stratara.Testing.Orleans&version=4.4.9
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.4.9)
- Stratara.Orleans.EntityFrameworkCore (>= 4.4.9)
- Stratara.Testing.EntityFrameworkCore (>= 4.4.9)
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 fix for hosts on the Orleans execution model. A host that removed or renamed a projection no longer has that
projection's store readers come back on every start and fail each entry; they retire once, as a saga's readers do. A
retired store reader now logs its retirement once instead of three times, and leaves no reminder error behind. No
API change, no schema change and no migration.
### Fixed
- **A reader of a removed projection retires.** On the Orleans execution model, a host that removed or renamed a
projection kept the keep-alive reminders of its store readers. On every start of the silo they brought the readers
back, and each one read the next entry of its partition, failed it because no projection of its name was
registered, and tried again on the next tick, without end — a warning per partition and entry. Such a reader now
retires the first time it is brought back, as a saga's reader already did: it unregisters its keep-alive, logs
`117_136` `UnregisteredProjectionReaderRetired` (Information) once, reads nothing and deactivates. Its checkpoints
stay, so a projection registered again resumes where it stopped; *Operate the Orleans execution model* says how to
delete them. In a rolling deployment that adds a projection, a reader that lands on a silo of the earlier version
refuses a rebuild's or a replay's pause, which then fails naming it, and a wait counts its partition as behind.
- **A retired store reader logs its retirement once.** A reader that retired as it was activated — of a partition
beyond a lowered partition count, or of a saga the silo no longer registers — deactivated before it answered the
call that activated it. Orleans forwarded that call to a new activation, which retired again, so the retirement was
logged three times per reader and the keep-alive tick ended in `Could not deliver reminder tick` at Error. The
reader now answers the call first and deactivates after it.