Support for "AnyTime-When" about mockhttp HOT 6 CLOSED

Interesting. Maybe we could have an optional BackendDefinitionBehavior enum as an argument to the MockHttpMessageHandler ctor, with values of NoExpectations (default) and Always.

This would still mean that expectations would still match before these whens if they both match the request, would that be acceptable?

from mockhttp.

Not sure if that entirely satisfies the circumstances I'm concerned about. Here's a step-by-step case example:

In the flow I'm executing, I expect requests A, B, and C to occur in the order given.

There is the possibility that request Z will fire off at any point in this flow. If it does, I want to define how to respond to it. Whether Z fires or not and regardless of when, I want the verification step to succeed if A, B, and C are all called in order and to fail if they were not.

from mockhttp.

The proposed solution works for the scenario you describe:

You would define A, B, and C via Expect; Z via When; and pass BackendDefinitionBehavior.Alwaysto the constructor.

A, B, and C would only only match in order, but Z would match anytime.

from mockhttp.

from mockhttp.

This will be released in version 3.2.0 (see #50 to explain the major version bump). I'll update this issue when it's out.

from mockhttp.

This was just released in 3.2.0

from mockhttp.