Skip to content

doc: Explain behaviour of when/expect #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

doc: Explain behaviour of when/expect #153

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0b6563
doc: Explain behaviour of when/expect
timabell Feb 28, 2025
f62a046
Note that `Expect` mocks have to be hit in the right order
timabell Mar 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,14 @@ Using `Expect` specifies a "Request Expectation". Request Expectations match onl

This pattern is heavily inspired by [AngularJS's $httpBackend](https://docs.angularjs.org/api/ngMock/service/$httpBackend)

If there are any `Expect` mocks present, then any `When` mocks will *not* be matched until *all* of the `Expect` mocks have had matching requests made. If you want to allow the `When` mocks to be matched even when there are outstanding `Expect` mocks then construct `MockHttpMessageHandler` with `BackendDefinitionBehavior.Always` instead of the default value of `BackendDefinitionBehavior.NoExpectations`:

```csharp
var mockHttp = new MockHttpMessageHandler(BackendDefinitionBehavior.Always);
```

Note that for `Expect` mocks the mocks have to be hit in the *same order* that they were set up. In other words, if you setup an `Expect` mock of a `POST` to `/first` and then a mock of a `POST` to `/second`, all http calls to `/second` will fail with "not matched" until a call to `/first` has been made.

### Matchers (With*)

The `With` and `Expect` methods return a `MockedRequest`, which can have additional constraints (called matchers) placed on them before specifying a response with `Respond`.
Expand Down