WireMock.Net.AwesomeAssertions 1.8.4
Prefix Reserveddotnet add package WireMock.Net.AwesomeAssertions --version 1.8.4
NuGet\Install-Package WireMock.Net.AwesomeAssertions -Version 1.8.4
<PackageReference Include="WireMock.Net.AwesomeAssertions" Version="1.8.4" />
<PackageVersion Include="WireMock.Net.AwesomeAssertions" Version="1.8.4" />
<PackageReference Include="WireMock.Net.AwesomeAssertions" />
paket add WireMock.Net.AwesomeAssertions --version 1.8.4
#r "nuget: WireMock.Net.AwesomeAssertions, 1.8.4"
#addin nuget:?package=WireMock.Net.AwesomeAssertions&version=1.8.4
#tool nuget:?package=WireMock.Net.AwesomeAssertions&version=1.8.4
WireMock.Net
Lightweight Http Mocking Server for .NET, inspired by WireMock.org (from the Java landscape).
⭐ Key Features
- HTTP response stubbing, matchable on URL/Path, headers, cookies and body content patterns
- Library can be used in unit tests and integration tests
- Runs as a standalone process, as windows service, as Azure/IIS or as docker
- Configurable via a fluent C# .NET API, JSON files and JSON over HTTP
- Record/playback of stubs (proxying)
- Per-request conditional proxying
- Stateful behaviour simulation
- Response templating / transformation using Handlebars and extensions
- Can be used locally or in CI/CD scenarios
- Can be used for Aspire Distributed Application testing
⭐ Stubbing
A core feature of WireMock.Net is the ability to return predefined HTTP responses for requests matching criteria. See Wiki : Stubbing.
⭐ Request Matching
WireMock.Net support advanced request-matching logic, see Wiki : Request Matching.
⭐ Response Templating
The response which is returned WireMock.Net can be changed using templating. This is described here Wiki : Response Templating.
⭐ Admin API Reference
The WireMock admin API provides functionality to define the mappings via a http interface see Wiki : Admin API Reference.
⭐ Using
WireMock.Net can be used in several ways:
UnitTesting
You can use your favorite test framework and use WireMock within your tests, see Wiki : UnitTesting.
Unit/Integration Testing using Testcontainers.DotNet
See Wiki : WireMock.Net.Testcontainers on how to build a WireMock.Net Docker container which can be used in Unit/Integration testing.
Unit/Integration Testing using an an Aspire Distributed Application
See Wiki : WireMock.Net.Aspire on how to use WireMock.Net as an Aspire Hosted application to do Unit/Integration testing.
As a dotnet tool
It's simple to install WireMock.Net as (global) dotnet tool, see Wiki : dotnet tool.
As standalone process / console application
This is quite straight forward to launch a mock server within a console application, see Wiki : Standalone Process.
As a Windows Service
You can also run WireMock.Net as a Windows Service, follow this WireMock-as-a-Windows-Service.
As a Web Job in Azure or application in IIS
See this link WireMock-as-a-(Azure)-Web-App
In a docker container
There is also a Linux and Windows-Nano container available at hub.docker.com. For more details see also Docker.
HTTPS / SSL
More details on using HTTPS (SSL) can be found here Wiki : HTTPS
📚 Documentation
For more info, see also this WIKI page: What is WireMock.Net.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. 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 was computed. 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. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.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 is compatible. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 is compatible. 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. |
.NETFramework 4.7
- AwesomeAssertions (>= 8.1.0)
- System.Text.RegularExpressions (>= 4.3.1)
- WireMock.Net (>= 1.8.4)
.NETStandard 2.0
- AwesomeAssertions (>= 8.1.0)
- System.Text.RegularExpressions (>= 4.3.1)
- WireMock.Net (>= 1.8.4)
.NETStandard 2.1
- AwesomeAssertions (>= 8.1.0)
- System.Text.RegularExpressions (>= 4.3.1)
- WireMock.Net (>= 1.8.4)
NuGet packages
This package is not used by any NuGet packages.
repositories
This package is not used by any popular repositories.
# 1.8.4 (08 May 2025)
- #1290 Use ILRepack to include Microsoft.OpenApi as internal [feature]
- #1275 WithMappingFromOpenApiFile - Support for OpenAPI 3.1.0 [feature]
The full release notes can be found here: https://.com/WireMock-Net/WireMock.Net/blob/master/CHANGELOG.md