Stratara.Testing.Orleans
4.4.2
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Testing.Orleans --version 4.4.2
NuGet\Install-Package Stratara.Testing.Orleans -Version 4.4.2
<PackageReference Include="Stratara.Testing.Orleans" Version="4.4.2" />
<PackageVersion Include="Stratara.Testing.Orleans" Version="4.4.2" />
<PackageReference Include="Stratara.Testing.Orleans" />
paket add Stratara.Testing.Orleans --version 4.4.2
#r "nuget: Stratara.Testing.Orleans, 4.4.2"
#:package Stratara.Testing.Orleans@4.4.2
#addin nuget:?package=Stratara.Testing.Orleans&version=4.4.2
#tool nuget:?package=Stratara.Testing.Orleans&version=4.4.2
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.11)
- Microsoft.Orleans.Server (>= 10.3.1 && < 11.0.0)
- Stratara.Orleans (>= 4.4.2)
- Stratara.Orleans.EntityFrameworkCore (>= 4.4.2)
- Stratara.Testing.EntityFrameworkCore (>= 4.4.2)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
A release about a flag that cost too much. Every host sharing the replay coordination state over Redis
asked Redis, with a blocking round trip on the calling thread, whether a replay was active — and the
Orleans execution model asked on every hot path, eight to ten times per command on a host with three
projections, inside grain turns. On a two-core host that was enough to starve the thread pool and time
the Redis connection out, surfacing as failed catch-ups, lagging read models and failed grain
registrations although no replay ever ran. The answer now comes from memory. No migration is needed;
one optional setting is new.
### Fixed
- **No path waits on Redis to learn whether a replay is active.** The Redis-backed replay state answers
`IsReplayActive` from a field. A change made in the host itself is seen there at once; a change made
elsewhere — a replay that began or ended in another host, or a marking that lapsed — is announced over
a channel beside the replay-request channel and seen within its latency, and every host re-reads the
marking every `ProjectionReplay:RefreshSeconds` regardless, as the safety net for a lost announcement.
The Orleans execution model's command dispatcher, bundle dispatcher, store readers and drain, and the
bus dispatchers, make no Redis call for it any more. Nothing changes for a host without Redis, whose
state was in process already, nor for a host that registers its own `IProjectionReplayState`.
### Added
- **`ProjectionReplayOptions.RefreshSeconds`** (default 5), read from the `ProjectionReplay` section
like the lease. It bounds how long a host answers from a replay marking that changed elsewhere where the
announcement was lost. Refused when the host starts at zero or below, and at or above
`LeaseSeconds`, with an `OptionsValidationException` naming `ProjectionReplay:RefreshSeconds`.
- **Log events `104_015` to `104_018`.** A host that cannot refresh the replay marking from Redis says
so once at Warning (`104_015`) and keeps its last answer; `104_016` at Information says it reads the
marking again. A host that cannot subscribe to the marking's announcements says so once at Warning
(`104_017`), sees a change on the refresh period only, and `104_018` says it is subscribed again.
### Changed
- **A host that cannot reach Redis keeps its last answer about the replay.** Before, every dispatch and
every catch-up on such a host failed with the connection's exception. Now they proceed on what the host
last learned — initially that no replay is active — and the loss is logged once. The replay stays
correct regardless: on the Orleans execution model the readers are paused by the rebuild and the
replay themselves, and apply the store from the beginning once more when the replay ends.
- **Rolling upgrade.** A host on a release before this one announces nothing when it starts or ends a
replay, so a host on this release sees that replay at the refresh period rather than at once. The
marking, its key and its lease are unchanged, so the two releases share one replay state.