starred/WireMock.Net
1
0
Fork 0
mirror of https://github.com/wiremock/WireMock.Net.git synced 2026-01-11 21:10:32 +01:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Updated Home (markdown)

Stef Heyenrath
2025-01-18 09:43:20 +01:00
parent eb27d41852
commit e7fc9b0bd8
1 changed files with 1 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
Home.md

@@ -1,31 +1 @@
# Welcome to the WireMock.Net wiki
## Stubbing & Request Matching
A core feature of WireMock is the ability to return predefined HTTP responses for requests matching criteria, [Stubbing](https://github.com/StefH/WireMock.Net/wiki/Stubbing) & [Request Matching](https://github.com/WireMock-Net/WireMock.Net/wiki/Request-Matching).
## Proxying
WireMock.Net has the ability to selectively proxy requests through to other hosts. This supports a proxy/intercept setup where requests are by default proxied to another (possibly real, live) service, but where specific stubs are configured these are returned in place of the remote service’s response. Responses that the live service can’t be forced to generate on demand can thus be injected for testing.
[Wiki : Proxying](https://github.com/StefH/WireMock.Net/wiki/Proxying).
## Record (via proxy) and Save
WireMock.Net has the ability to create stub mappings by recording them while you send requests. This can be used to quickly capture a collection of responses from a real service then use them offline in your tests.
[Wiki : Proxy and Record) and Save](https://github.com/WireMock-Net/WireMock.Net/wiki/Settings#proxyandrecordsettings).
## Scenarios ##
WireMock.Net supports state via the notion of scenarios. A scenario is essentially a state machine whose states can be arbitrarily assigned. See [Wiki : Scenarios and States](https://github.com/WireMock-Net/WireMock.Net/wiki/Scenarios-and-Statefull-behaviour)
## Using WireMock.Net in UnitTest framework
You can use your favorite test framework and use WireMock within your tests, see
[Wiki : UnitTesting](https://github.com/StefH/WireMock.Net/wiki/Using-WireMock-in-UnitTests).
## Admin API Reference
The WireMock admin API provides functionality to define the mappings via a http interface, see [Wiki : Admin API Reference](https://github.com/StefH/WireMock.Net/wiki/Admin-API-Reference).
## WireMock as a standalone process
This is quite straight forward to launch a mock server within a console application, see [Wiki : standalone](https://github.com/StefH/WireMock.Net/wiki/WireMock-as-a-standalone-process).
## WireMock hosted in IIS or Azure
It's also possible to run in IIS or as a WebApp in Azure. See [Wiki: IIS/Azure](https://github.com/WireMock-Net/WireMock.Net/wiki/WireMock-as-a-(Azure)-Web-App)
## WireMock as Windows Service
See [Wiki : Windows Service](https://github.com/WireMock-Net/WireMock.Net/wiki/WireMock-as-a-Windows-Service) on how to run as a Windows service.
# Welcome to the WireMock.Net wiki