NResilience.Testing 0.14.0

NResilience.Testing

Test helpers for NResilience: scripted callbacks, a recording telemetry listener, and fake-time support for deterministic, fast tests.

Install

Install the package using the .NET CLI:

dotnet add package NResilience.Testing

Why a separate package

Testing retries and timeouts against the real clock is slow and flaky - a 30-second timeout takes 30 seconds to test, and timing varies across machines. NResilience.Testing lets you script dependency behavior, capture policy events for assertion, and advance time manually, so a timeout test runs in microseconds.

It is a test-time dependency only and does not affect the core library in production.

Script the callback

Sequence<T> serves a script of returns, throws, and delays one by one as the policy makes attempts:

Sequence<HttpResponseMessage> calls = Sequence.For<HttpResponseMessage>()
    .Returns(new HttpResponseMessage(HttpStatusCode.ServiceUnavailable), count: 2)
    .Returns(new HttpResponseMessage(HttpStatusCode.OK));

var policy = Resilience.Http with { Backoff = Backoff.None };

CallResult<HttpResponseMessage> result = await policy.TryRunAsync(attempt => calls.NextAsync(attempt));

Assert.True(result.IsSuccess);
Assert.Equal(3, calls.CallCount);
Assert.Equal(3, result.Attempts.Count);

Control the clock

Pass the same FakeTimeProvider to both the policy and the sequence to test timeouts without waiting:

var time = new FakeTimeProvider();

Sequence<int> calls = Sequence.For<int>(time)
    .Delays(TimeSpan.FromSeconds(30))   // longer than the attempt timeout
    .Returns(1);

var policy = Resilience.Default with
{
    Time = time,
    Attempts = 1,
    AttemptTimeout = TimeSpan.FromSeconds(3),
};

Task<CallResult<int>> pending = policy.TryRunAsync(attempt => calls.NextAsync(attempt)).AsTask();
time.Advance(TimeSpan.FromSeconds(4));

CallResult<int> result = await pending;

Assert.IsType<AttemptTimeoutException>(result.Exception);

Verify policy behavior

EventRecorder captures every CallEvent in order, so you can assert on the sequence rather than elapsed time:

var events = new EventRecorder();
Sequence<int> calls = Sequence.For<int>().Throws(new IOException()).Returns(42);

var policy = Resilience.Default with { Backoff = Backoff.None, OnEvent = events.Record };

await policy.RunAsync(attempt => calls.NextAsync(attempt));

Assert.Equal(
    [CallEventKind.Attempt, CallEventKind.Retrying, CallEventKind.Attempt, CallEventKind.Succeeded],
    events.Kinds);

Reach for a ready-made policy

TestPolicy.Instant is a Resilience value shaped for tests: three attempts, no backoff, and both the deadline and the attempt timeout set to infinite, so a test pays for neither a sleep nor a wall-clock bound it does not care about. TestPolicy.InstantHttp is the same shape with Classify = Classifier.Http.

var api = TestPolicy.Instant;

To run Instant on a FakeTimeProvider, call TestPolicy.On(time). It rebuilds any breaker the policy carries on that same clock, so the policy, its breaker and its budget all advance together:

var time = new FakeTimeProvider();
var api = TestPolicy.On(time);

Test an HTTP client

Provide a scripted HttpMessageHandler as the inner handler to test a resilient HttpClient end to end. ScriptedHttpHandler serves the script you give it, then repeats the last step for every attempt after that:

var transport = new ScriptedHttpHandler()
    .Respond(HttpStatusCode.ServiceUnavailable)
    .Respond(HttpStatusCode.OK);

using HttpClient client = ResilienceHttp.CreateClient(
    Resilience.Http with { Backoff = Backoff.None },
    innerHandler: transport);

using HttpResponseMessage response = await client.GetAsync(new Uri("https://api.example.com/orders/1"));

Assert.Equal(HttpStatusCode.OK, response.StatusCode);
Assert.Equal(2, transport.CallCount);

Respond(status) and Respond(status, times) serve a fixed status code, once or for a run of attempts. Respond(response) and Respond(response, times) build a fresh HttpResponseMessage per attempt, for a response whose content a test reads. Throw(exception) and Throw(exception, times) throw instead, for the transport failures a classifier has to see.

CallCount is how many attempts reached the handler. Requests is a snapshot of what each attempt sent, in order: the method, the URI, the headers, and - only when CaptureBodies is true - the body.

Documentation

For more information, see the following resources:

• Testing guide - the full walkthrough, including best practices for keeping tests fast and deterministic.

Feedback

Provide feedback using these channels:

• Usage questions
• Bug reports and feature requests
• Security vulnerabilities - private advisory, not a public issue.