A C# .NET version based on mock4net which mimics the functionality from the JAVA based WireMock.org.

• 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

Project
Chat
Issues
Quality
Build
Build Azure
CodeFactor
Sonar Quality Gate
Sonar Bugs
Sonar Code Smells
Sonar Coverage
Coveralls
Nuget
WireMock.Net
WireMock.Net.StandAlone

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.

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.

This is quite straight forward to launch a mock server within a console application, see Wiki : Standalone Process.

You can also run WireMock.Net as a Windows Service, follow this WireMock-as-a-Windows-Service.

See this link WireMock-as-a-(Azure)-Web-App

There is also a Linux and Windows-Nano container available at hub.docker.com. For more details see also Docker.

More details on using HTTPS (SSL) can be found here Wiki : HTTPS