dotnet add package WireMock.Net.Abstractions --version 1.5.36
NuGet\Install-Package WireMock.Net.Abstractions -Version 1.5.36
<PackageReference Include="WireMock.Net.Abstractions" Version="1.5.36" />
paket add WireMock.Net.Abstractions --version 1.5.36
#r "nuget: WireMock.Net.Abstractions, 1.5.36"
// Install WireMock.Net.Abstractions as a Cake Addin #addin nuget:?package=WireMock.Net.Abstractions&version=1.5.36 // Install WireMock.Net.Abstractions as a Cake Tool #tool nuget:?package=WireMock.Net.Abstractions&version=1.5.36
Lightweight Http Mocking Server for .NET, inspired by [WireMock(http://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
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.
WireMock.Net can be used in several ways:
You can use your favorite test framework and use WireMock within your tests, see Wiki : UnitTesting.
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
HTTPS / SSL
More details on using HTTPS (SSL) can be found here Wiki : HTTPS
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.|
|.NET Core||netcoreapp1.0 was computed. netcoreapp1.1 was computed. netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed.|
|.NET Standard||netstandard1.0 is compatible. netstandard1.1 was computed. netstandard1.2 was computed. netstandard1.3 is compatible. netstandard1.4 was computed. netstandard1.5 was computed. netstandard1.6 was computed. netstandard2.0 is compatible. netstandard2.1 is compatible.|
|.NET Framework||net45 is compatible. net451 is compatible. net452 was computed. net46 was computed. net461 is compatible. 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||tizen30 was computed. tizen40 was computed. tizen60 was computed.|
|Universal Windows Platform||uap was computed. uap10.0 was computed.|
|Windows Phone||wp8 was computed. wp81 was computed. wpa81 was computed.|
|Windows Store||netcore was computed. netcore45 was computed. netcore451 was computed.|
|Xamarin.iOS||xamarinios was computed.|
|Xamarin.Mac||xamarinmac was computed.|
|Xamarin.TVOS||xamarintvos was computed.|
|Xamarin.WatchOS||xamarinwatchos was computed.|
- No dependencies.
- No dependencies.
- No dependencies.
- NETStandard.Library (>= 1.6.1)
NuGet packages (8)
Showing the top 5 NuGet packages that depend on WireMock.Net.Abstractions:
Lightweight Http Mocking Server for .Net, inspired by WireMock from the Java landscape.
An OpenApi (swagger) parser to generate MappingModel or mapping.json file.
A RestClient using RestEase to access the admin interface.
FluentAssertions extensions for WireMock.Net
Some extensions for xUnit (ITestOutputHelper)
GitHub repositories (1)
Showing the top 1 popular GitHub repositories that depend on WireMock.Net.Abstractions:
WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality.
# 1.5.36 (21 September 2023)
- #986 Write logging in case a Matcher throws an exception [feature]
- #996 Remove dependency on Microsoft.AspNet.WebApi.Client [feature]
- #1002 Fixed logic for SaveUnmatchedRequests [bug]
- #974 HttpClient extension methods causes ambiguous invocations in .NET 7 [bug]
- #1001 SaveUnmatchedRequests stopped working [bug]
The full release notes can be found here: https://github.com/WireMock-Net/WireMock.Net/blob/master/CHANGELOG.md