- HTTP response stubbing, matchable on URL/Path, headers, cookies and body content patterns
- Runs in unit tests, as a standalone process, as windows service, as Azure or IIS or as docker
- Configurable via a fluent DotNet API, JSON files and JSON over HTTP
- Record/playback of stubs
- Per-request conditional proxying
- Stateful behaviour simulation
- Configurable response delays
|Sonar Quality Gate|
|Sonar Code Smells|
For the supported frameworks and build information, see this page.
A core feature of WireMock.Net is the ability to return predefined HTTP responses for requests matching criteria. See Wiki : Stubbing.
WireMock.Net support advanced request-matching logic, see Wiki : Request Matching.
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 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