Stratara.Testing.Orleans 4.7.0

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.7.0
                    
NuGet\Install-Package Stratara.Testing.Orleans -Version 4.7.0
                    
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.7.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Testing.Orleans" Version="4.7.0" />
                    
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.7.0
                    
#r "nuget: Stratara.Testing.Orleans, 4.7.0"
                    
#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.7.0
                    
#: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.7.0
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Testing.Orleans&version=4.7.0
                    
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 release for one person who belongs to several tenants — and, sharing one identity store, to several applications.

### Added

- **`MembershipStatus.Former`** records a member who has left. It confers nothing — no role, permission or
 cross-tenant access, never the tenant at sign-in, never a selection — and stays listed until the user's or the
 tenant's erasure removes it.
- **`AddCheckedMembershipTenantClaim<TUser>()`**, a third tenant-claim mode: the claim is stamped at sign-in, kept when
 the security-stamp validator refreshes a cookie sign-in, and checked on every request. A request whose user is no
 longer an active member of the carried tenant loses the claim and resolves to the reserved default tenant, without
 another tenant substituted. Only principals ASP.NET Identity issued are checked; an API key or a token the host
 mints keeps its tenant. The tenant changes only when the host re-issues the sign-in. Combining it with
 `AddMembershipTenantClaimsTransformation()` throws, and a claims transformation of the host's own registered
 beside it is refused at start. Use it where several applications share one identity store:
 `active_tenant` holds one selection per account, so live resolution moves every open session when any of them
 switches.
- **`EventSubject.ForUser(userId)`** and **`EventSubject.NamesAnOwner`**: a stream can be created for a user alone,
 for data that belongs to a person rather than to any of their tenants. It is recorded under the reserved default
 tenant, keeps that owner for every later event whatever tenant the session names, and its encrypted fields — at
 every level — are keyed to the person: shredded by the person's erasure, untouched by any tenant's.
 `KeySubject.User` covers those keys too, so nothing is encrypted for the person again after the erasure.

- **`StrataraIdentityStore`, an identity store several hosts can share on PostgreSQL**, with its migrations shipped
 in `Stratara.EventSourcing.EntityFrameworkCore`. It holds ASP.NET Identity's tables, passkeys included, and the
 tenant directory in the fixed schema `stratara_identity`, with the history in
 `stratara_identity.__stratara_identity_migrations`. `AddStrataraIdentityStore()` registers it on the connection
 string `identitydb` (falling back to `defaultdb`, never through a tenant-routing `IDbResolver`) with the
 directory's stores over it, and refuses a host that turns on `Stores.ProtectPersonalData`;
 `MigrateStrataraIdentityStoreAsync()` creates the database where needed and applies the migrations — hosts that
 migrate at once take turns. The account type is `IdentityUser` and cannot be extended, and the store fixes the
 ASP.NET Identity schema version and key lengths, so every host's model matches the shipped migrations. Within a
 major version the schema changes only additively. Moving an existing identity store onto it means replacing it and
 seeding with the same user and tenant ids; the new guide *Shared Identity Store* describes it.

### Changed

- **Setting a membership to a status other than `Active` clears a selection that pointed at it**, as removing it
 already did.
- **An explicit subject that names a user and no tenant is accepted** by `AppendOnBehalfOfAsync` and
 `CreateOnBehalfOfAsync`; one that names neither is refused as before. A session whose tenant resolved to the
 reserved default still gives an event no owner.
- **BREAKING (behaviour): an event or aggregate type marked `[EncryptData]` as a whole stops the host from starting.**
 `EncryptionMetadataDriftGuard` refuses every registered aggregate, and every event type a registered aggregate
 applies, that carries the attribute on the type; an event type no aggregate applies is refused when it is appended,
 before anything is written. Once its subject was erased such a payload had nothing left to deliver, and a replay or
 rebuild stopped there for good. Mark the properties instead; payloads already written as a whole are still read.
 Commands and other types may still be marked as a whole.

### Fixed

- **A user's erasure shreds their own data through a key store that cannot list its scopes.** The eraser names the
 user's keys under the reserved default tenant itself, at every level; until now only a listing reached the
 user-level one.