Stratara.Testing.Orleans 4.4.8

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Testing.Orleans --version 4.4.8
                    
NuGet\Install-Package Stratara.Testing.Orleans -Version 4.4.8
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Stratara.Testing.Orleans" Version="4.4.8" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Testing.Orleans" Version="4.4.8" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Testing.Orleans" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Stratara.Testing.Orleans --version 4.4.8
                    
#r "nuget: Stratara.Testing.Orleans, 4.4.8"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Stratara.Testing.Orleans@4.4.8
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Stratara.Testing.Orleans&version=4.4.8
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Testing.Orleans&version=4.4.8
                    
Install as a Cake Tool

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 preset Session and Services. IAsyncDisposable.
  • ExecutionModelTestHostOptions — the periods (PollInterval 250 ms, ReminderPeriod 1 s, IntentGrace 2 s, DrainPollingInterval 1 s), the partition count (4), the start timeout, and BeforeStart, 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=true opts out, as the sample does. CreateAsync refuses to run where DOTNET_ENVIRONMENT or ASPNETCORE_ENVIRONMENT states an environment other than Development.

Dependencies

  • Stratara.Orleans, Stratara.Orleans.EntityFrameworkCore, Stratara.Testing.EntityFrameworkCore
  • Microsoft.Orleans.Server, Microsoft.Extensions.Hosting
Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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 store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.

### Fixed

- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
 saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
 behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
 keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
 catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
 running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
 catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
 overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
 longer than the response timeout on another silo waited for that run in its own start. The start then failed
 with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
 interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
 still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
 the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
 work rather than a busy one.