TestableHttpClient 0.11.26
dotnet add package TestableHttpClient --version 0.11.26
NuGet\Install-Package TestableHttpClient -Version 0.11.26
<PackageReference Include="TestableHttpClient" Version="0.11.26" />
paket add TestableHttpClient --version 0.11.26
#r "nuget: TestableHttpClient, 0.11.26"
// Install TestableHttpClient as a Cake Addin #addin nuget:?package=TestableHttpClient&version=0.11.26 // Install TestableHttpClient as a Cake Tool #tool nuget:?package=TestableHttpClient&version=0.11.26
TestableHttpClient
Creating unittest for code that uses HttpClient
can be difficult to test. It requires a custom HttpMessageHandler or a mocked version. TestableHttpClient provides a testable version of HttpMessageHandler and several helper functions to configure the TestableHttpHandler
and several ways to assert which requests were made.
How to install
TestableHttpClient is released as a NuGet packages and can be installed via the NuGet manager in VisualStudio or by running the following command on the command line:
dotnet add package TestableHttpClient
How to use TestableHttpClient
The following code block shows the basic use case for asserting that certain requests are made:
TestableHttpMessageHandler testHandler = new();
HttpClient httpClient = new(testHandler); // or testHandler.CreateClient();
var result = await httpClient.GetAsync("http://httpbin.org/status/200");
testHandler.ShouldHaveMadeRequestsTo("https://httpbin.org/*");
The default response is an empty response message with a 200 OK StatusCode, in order to return real content the response need to be configured:
TestableHttpMessageHandler testHandler = new();
testHandler.RespondWith(Responses.Json(new { Hello: "World" }));
HttpClient httpClient = new(testHandler); // or testHandler.CreateClient();
var result = await httpClient.GetAsync("http://httpbin.org/status/200");
testHandler.ShouldHaveMadeRequestsTo("https://httpbin.org/*");
More examples can be found in the IntegrationTests project
URI Patterns
TestableHttpClient supports URI patterns in several places, mainly in:
- Response routing, where an URI pattern is used for matching the request URI to a response
- Assertions, where requests can be asserted against an URI pattern.
URI patterns are based on URI's as specified in RFC 3986, but allow the wildcard character *
to specify optional parts of an URI.
An URI contains several components:
- The scheme of an URI is optional, but when given it should end with
://
. When not given*://
is assumed. - User Information (
username:password@
) is ignored and is not checked at all. - The host is optional and when not given
*
is assumed. Both IP addresses and registered names are supported. - The port is optional, but when ':' is provided after host, it should have a value.
- The path is optional, but should start with a
/
. When/
is given, it can be followed by a*
to match it with any path. - Query parameters are optional, when given it should start with a
?
. - Fragments are ignored, but should start with a
#
.
URI patterns differ from URI's in the following ways:
- Any character is allowed, for example:
myhost:myport
is a valid URI pattern, but not a valid URI. (and this will never match). - No encoding is performed, and patterns are matched against the unescaped values of an URI.
- Patterns are not normalized, so a path pattern
/test/../example
will not work.
Some examples:
Uri pattern | Matches |
---|---|
* | Matches any URL |
*://*/*?* | Matches any URL |
/get | Matches any URL that uses the path /get |
http*://* | Matches any URL that uses the scheme http or https (or any other scheme that starts with http ) |
localhost:5000 | Matches any URL that uses localhost for the host and port 5000, no matter what scheme or path is used. |
Controlling the behaviour of pattern matching
TestableHttpClient has several options available that let you control different parts of the library. These options can be found on
the TestableHttpMessageHandler.Options
and are passed to the HttpRepsonseContext
and the IHttpRequestMessagesCheck
.
The options include:
JsonSerializerOptions
for controlling the serialization of json contentUriPatternMatchingOptions
for controlling how the URI pattern matching works.
Supported .NET versions
TestableHttpClient is build as a netstandard2.0 library, so theoretically it can work on every .NET version that support netstandard2.0. The following versions are being actively tested and thus supported:
- .NET Framework 4.6, 4.7 and 4.8
- .NET 6.0
- .NET 8.0
These versions are supported as long as Microsoft supports them, we do our best to test and support newer versions as soon as possible.
Contributing
Please read CONTRIBUTING.md for details on how you can help us out.
Versioning
We use SemVer for versioning. For the versions available, see the releases on this repository.
Note that currently every library will always be released when a new tag is created, even though it might not have any changes.
Authors
- David Perfors - dnperfors
See also the list of contributors who participated in this project.
License
This project is released under the MIT license, see LICENSE.md for more information.
Acknowledgments
This project is largely inspired by the HttpTest functionality from Flurl.
A lot of the ideas came from the thread about unit testing HttpClient code in this dotnet issue.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. 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. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Perfors.UnreachableException (>= 1.0.0)
- PolyKit.Embedded (>= 3.0.9)
- System.Net.Http (>= 4.3.4)
- System.Text.Json (>= 4.6.0)
-
net6.0
- Perfors.UnreachableException (>= 1.0.0)
-
net8.0
- No dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on TestableHttpClient:
Package | Downloads |
---|---|
TestableHttpClient.NFluent
NFluent checks for checking HttpResponseMessages. |
GitHub repositories
This package is not used by any popular GitHub repositories.
All release notes for TestableHttpClient can be found on the GitHub site - https://github.com/testablehttpclient/TestableHttpClient/releases