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.
A C# .NET version based on mock4net which mimics the functionality from the JAVA based WireMock.
For more info, see also this WIKI page: What is WireMock.Net.
Project | |
Chat | |
Issues | |
Quality | |
Build Azure | |
Quality | |
Sonar Bugs | |
Coverage |
Official | Preview :information_source: | |
---|---|---|
WireMock.Net | ||
WireMock.Net.StandAlone | ||
WireMock.Net.FluentAssertions | ||
WireMock.Net.Matchers.CSharpCode | ||
WireMock.Net.OpenApiParser | ||
WireMock.Net.RestClient | ||
WireMock.Net.xUnit | ||
WireMock.Net.Testcontainers | ||
WireMock.Org.RestClient |
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.
You can use Wiki : WireMock.Net.Testcontainers to build a WireMock.Net Docker container which can be used in Unit/Integration testing.
It's simple to install WireMock.Net as (global) dotnet tool, see Wiki : dotnet tool.
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