LoadStrike 1.0.23601

dotnet add package LoadStrike --version 1.0.23601
                    
NuGet\Install-Package LoadStrike -Version 1.0.23601
                    
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="LoadStrike" Version="1.0.23601" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="LoadStrike" Version="1.0.23601" />
                    
Directory.Packages.props
<PackageReference Include="LoadStrike" />
                    
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 LoadStrike --version 1.0.23601
                    
#r "nuget: LoadStrike, 1.0.23601"
                    
#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 LoadStrike@1.0.23601
                    
#: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=LoadStrike&version=1.0.23601
                    
Install as a Cake Addin
#tool nuget:?package=LoadStrike&version=1.0.23601
                    
Install as a Cake Tool

LoadStrike SDK for .NET

LoadStrike is a developer-first load testing SDK for .NET applications, services, and automated test projects. Use it to model transaction flows in C#, execute them in-process, and capture structured run results from the same solution that owns the code under test.

What This SDK Is For

  • Author scenario-based load tests in C#.
  • Generate safe starter scenarios from captured HAR, OpenTelemetry trace JSON, browser recordings, or message pairs with Trace-to-test Autopilot.
  • Model HTTP and event-driven transactions as multi-step workflows.
  • Apply load simulations, thresholds, and custom metrics during execution.
  • Generate local reports and, on Business and Enterprise, publish results to supported reporting sinks.

Built-in transport coverage includes HTTP, Kafka, RabbitMQ, NATS, Redis Streams, Azure Event Hubs, Push Diffusion, and delegate-based custom streams. Local report output supports HTML, Markdown, TXT, and CSV, and Business and Enterprise can publish to InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OpenTelemetry Collector.

Requirements

  • .NET 8 or later

Install

dotnet add package LoadStrike

Quick Start

using System;
using System.Threading.Tasks;
using LoadStrike;

var scenario = LoadStrikeScenario.Create("orders", async context =>
{
    var step = await LoadStrikeStep.Run<string>(
        "publish-order",
        context,
        () => Task.FromResult(LoadStrikeResponse.Ok<string>(statusCode: "200")));

    return step.AsReply();
})
.WithLoadSimulations(
    LoadStrikeSimulation.Inject(10, TimeSpan.FromSeconds(1), TimeSpan.FromSeconds(20))
);

var result = LoadStrikeRunner.RegisterScenarios(scenario)
    .WithRunnerKey("rkl_your_runner_key")
    .Run();

Run() returns the detailed run result, including generated report files, scenario statistics, metrics, and sink status.

Trace-To-Test Autopilot

Use LoadStrikeAutopilot.Generate(...) to infer a starter plan from a captured artifact. Set LoadStrikeAutopilotOptions.RunnerKey so generation can validate the Trace-To-Test Autopilot entitlement. Check result.Readiness and result.ReadinessFailures first; call result.BuildScenario() only when it is LoadStrikeAutopilotReadiness.Ready, then execute the scenario through the normal runner with a valid RunnerKey.

Use SecretBindings to map redaction locations such as header:Authorization or body:$.client_secret to environment variables, TrackingSelector when the selector cannot be inferred, and EndpointBindings, AllowedReplayHosts, or BaseUrlRewrite when a replay target must be bound. Secret values are resolved when the generated scenario runs; they are not written into the generated plan. Any gate satisfied by user setup is omitted from ReadinessFailures.

Runner Keys

Runnable workloads require a RunnerKey. Supply it with .WithRunnerKey(...) or through your application configuration before calling Run().

Documentation

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  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
1.0.23601 92 5/12/2026
1.0.23401 89 5/12/2026
1.0.23201 90 5/11/2026
1.0.23001 99 5/9/2026
1.0.22801 87 5/8/2026
1.0.22601 88 5/4/2026
1.0.22301 104 5/1/2026
1.0.22001 104 4/27/2026
1.0.21401 97 4/24/2026
1.0.21101 87 4/23/2026
1.0.20801 104 4/21/2026
1.0.18901 94 4/19/2026
1.0.18001 97 4/10/2026
1.0.17501 96 4/9/2026
1.0.17301 99 4/9/2026
Loading failed