StoveDotnet.Azure.ServiceBus 0.2.0

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

StoveDotnet

TL;DR

StoveDotnet removes the infrastructure-orchestration boilerplate from realistic .NET end-to-end tests.

It starts containerized databases, brokers, caches, and other dependencies; injects their connection details into your real ASP.NET Core or worker applications; waits for the system to become ready; and owns cleanup. Tests use a focused DSL to call applications, prepare state, publish or observe messages, query databases, and inspect telemetry. Correlation, bounded waits, validation helpers, and failure evidence make tests easier to write and diagnose. Without locking you into a test framework or assertion library.

CI Documentation NuGet OpenSSF Scorecard

Opinionated end-to-end testing for .NET, inspired by Trendyol Stove.

Documentation · Compatibility and trust · NuGet packages · Roadmap · Security

StoveDotnet starts your real dependencies in containers, injects their connection details into your real application, runs the application in-process on a real Kestrel port, and gives every test one fluent DSL to arrange and assert across HTTP, PostgreSQL, SQL Server, MongoDB, MySQL, Kafka, RabbitMQ, Azure Service Bus, Redis and third-party HTTP APIs. Stove captures the application's logs and traces in-process so a failing test explains itself.

[Fact]
public Task Creates_order_when_stock_is_available() => stove.Test(async t =>
{
    t.InventoryFake().StockAvailable("chair", available: 5);           // typed fakes generated from OpenAPI specs
    var payments = t.PaymentsFake().ChargeSucceeds(paymentId: "pay-1");

    var response = (await t.Http().Post<Order>("/orders", new CreateOrderRequest("chair", 2, "customer-1")))
        .Expect(HttpStatusCode.Created);

    var statuses = await t.Postgres().Query(
        "select status from orders where id = @id", r => r.GetString(0),
        new NpgsqlParameter("id", response.Body.Id));
    Assert.Equal(["Created"], statuses);

    await t.Kafka().ShouldBePublished<OrderCreated>(m => m.Value.OrderId == response.Body.Id);
    var charge = await payments.ShouldHaveCharged(c => c.OrderId == response.Body.Id);
    Assert.Equal(20m, charge.Amount);
});

Principles

  • The real system runs. Stove does not automatically replace application services. Overrides are explicit through the host hook; optional UseStoveTime(clock) registers a fixture-owned test clock.
  • Every e2e test goes through stove.Test. The test is named after its method. Systems are reachable only through the test context t. Stove owns the test's scope: correlation, per-test cleanup and failure reporting.
  • No test framework lock-in. Stove ships no xUnit, NUnit, TUnit or MSTest extensions. You start Stove once per test run from your framework's hook (see Test frameworks).
  • Use your assertion library. DSL methods return values or take callbacks; HTTP also offers fluent status checks.
  • Lightweight. No dashboard, no agents and no collector. Traces and logs are captured in the test process.

Packages

Package Provides
StoveDotnet Builder, lifecycle, stove.Test, correlation, Eventually, migrations
StoveDotnet.AspNetCore WithAspNetCoreApplication<Program>() (WebApplicationFactory + real Kestrel)
StoveDotnet.Hosting WithHostApplication("worker", factory): named Generic Host workers with configuration and managed shutdown; DI bridge t.Using<T>() and opt-in test time (UseStoveTime(clock), t.Clock(application)) for any application
StoveDotnet.Containers WithContainer("storage", configure): bring your own Testcontainers image, readiness, initialization and application configuration
StoveDotnet.Http t.Http(): typed JSON calls against the application
StoveDotnet.Oidc WithOidc() / t.Oidc(): local discovery, JWKS and signed test tokens for real bearer validation
StoveDotnet.Telemetry WithTelemetry(): in-process trace capture per test, t.Telemetry()
StoveDotnet.Postgres WithPostgres(): Testcontainers PostgreSQL, raw Npgsql DSL
StoveDotnet.SqlServer WithSqlServer(): Testcontainers SQL Server, native Microsoft.Data.SqlClient DSL
StoveDotnet.MongoDb WithMongoDb(): MongoDB replica set, native filters, collections and ordered setup
StoveDotnet.MySql WithMySql(): MySQL, native MySqlConnector DSL
StoveDotnet.Kafka WithKafka(): Testcontainers Kafka, black-box publish/consume/fail assertions
StoveDotnet.SchemaRegistry WithSchemaRegistry(): Confluent registry with ordered schema setup migrations
StoveDotnet.Kafka.Avro WithKafkaAvro(): generated Avro event publishing and observation using registry schema IDs
StoveDotnet.RabbitMq WithRabbitMq(): confirmed publishing, dedicated observation queues, native RabbitMQ.Client
StoveDotnet.Azure.ServiceBus WithAzureServiceBus(): official emulator or Azure namespace, typed topology, scheduling and explicit settlement
StoveDotnet.Redis WithRedis(): Testcontainers Redis, StackExchange.Redis client
StoveDotnet.WireMock WithWireMock(): in-process WireMock.Net servers

Requirements: .NET 10 and a Docker-compatible container runtime (Docker or Podman) for the container modules.

The packages are in preview on nuget.org and are released together: use the same version of every StoveDotnet package. Install the ones you need into your e2e test project:

dotnet add package StoveDotnet.AspNetCore --prerelease
dotnet add package StoveDotnet.Http --prerelease
dotnet add package StoveDotnet.Postgres --prerelease

Setting up

Describe the environment once and start it from your test framework's once-per-run hook:

Stove = await StoveBuilder.Create()
    .WithTelemetry()
    .WithPostgres(o => o.ConfigureExposedConfiguration = c => [new("ConnectionStrings:Orders", c.ConnectionString)])
    .WithRedis(o => o.ConfigureExposedConfiguration = c => [new("ConnectionStrings:Redis", c.ConnectionString)])
    .WithKafka(o =>
    {
        o.ConfigureExposedConfiguration = c => [new("Kafka:BootstrapServers", c.BootstrapServers)];
        o.Migrations.Add((ctx, _) => ctx.Admin.CreateTopicsAsync([new TopicSpecification { Name = "orders.created" }]));
    })
    .WithWireMock("inventory", o => o.ConfigureExposedConfiguration = c => [new("Inventory:BaseUrl", c.BaseUrl.ToString())])
    .WithWireMock("payments", o => o.ConfigureExposedConfiguration = c => [new("Payments:BaseUrl", c.BaseUrl.ToString())])
    .WithHttpClient()
    .WithAspNetCoreApplication<Program>()
    .StartAsync();

Each system exposes typed connection details; ConfigureExposedConfiguration maps them to the configuration keys your application already reads. Stove starts the dependencies in parallel, runs their migrations, starts the application with that configuration, and owns cleanup.

When a test fails

Stove rethrows the failure as a StoveTestFailedException. The original exception is kept as InnerException, and the message contains what each system observed for that test:

StoveDotnet.StoveTestFailedException : EqualException: Assert.Equal() Failure: Values differ
Expected: Created
Actual:   PaymentRequired

Stove test: OrderTests.Failure_output_demo
Trace id:   b23be8492d7e283bae0f7b389e58a5fc

--- Stove: application:(default) / application logs ---
09:42:49.016 [Warning] OrderService.OrderWorkflow: Payment declined for order 6de533c8-... of customer customer-4

--- Stove: telemetry ---
[x] POST http://127.0.0.1:58643/orders (System.Net.Http, Client, 356.8ms)
`-- [ok] POST /orders (Microsoft.AspNetCore, Server, 347.8ms)
    |-- [ok] GET http://localhost:58630/stock/sofa (System.Net.Http, Client, 260.8ms)
    |   `-- [ok] GET (Microsoft.AspNetCore, Server, 246.7ms)
    `-- [x] POST http://localhost:58631/charges (System.Net.Http, Client, 29.2ms)
        `-- [x] POST (Microsoft.AspNetCore, Server, 25.8ms)

--- Stove: wiremock 'payments' ---
Requests received (1):
  POST http://localhost:58631/charges -> 500 (matched) {"orderId":"6de533c8-...","customerId":"customer-4","amount":10}

--- Stove: http ---
Requests sent (1):
  POST http://127.0.0.1:58643/orders → 402 PaymentRequired (356.8ms)
    Response body: (empty)

The report does not depend on how the test asserted or on which assertion library you use. Application logs and the requests the test sent need no setup; the trace tree comes from WithTelemetry(). See telemetry and failure reports for what each section contains and how tests are correlated.

Test frameworks

Runnable examples demonstrate xUnit v3, NUnit, MSTest and TUnit, each with its own lifecycle hooks and native assertions against the same real ASP.NET Core application, PostgreSQL container and WireMock catalog.

See the adopter guide for package setup, cancellation, parallelism and single-test commands, and the example projects for code you can run and adapt. The examples target .NET 10 with Microsoft.Testing.Platform. CI checks normal, filtered, failed and skipped runs, verifies teardown, and repeats the checks against isolated NuGet consumers before publishing.

AI agents

StoveDotnet ships an agent skill that teaches coding agents to:

  • set up Stove in a project;
  • write tests with the correct APIs;
  • read failure output;
  • generate typed WireMock fakes from OpenAPI specs or SDK definitions.

The skill uses the open SKILL.md format.

  • Claude Code: install it as a plugin:
    /plugin marketplace add cokceken/stove-dotnet
    /plugin install stove-dotnet@stove-dotnet
    
  • Other agents (Codex, GitHub Copilot, Cursor and others that read .agents/skills): copy plugins/stove-dotnet/skills/stove-dotnet into your repository's .agents/skills/ (or .claude/skills/).

Then ask, for example: "Add Stove e2e tests for the order endpoint" or "Create a WireMock fake for the payments API from specs/payments.yaml".

Contributing

See CONTRIBUTING.md for the repository layout, building, the test suites and the release process, and the roadmap for what is planned.

License

Apache-2.0

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
0.2.0 0 11/16/2026
0.2.0-preview.2 7 11/16/2026
0.1.6 153 10/12/2026
0.1.5 122 9/30/2026
0.1.3 135 9/26/2026