mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-02-25 18:25:10 +01:00
33 lines
2.0 KiB
Markdown
33 lines
2.0 KiB
Markdown
# WireMock.Net
|
|
A C# .NET version based on https://github.com/alexvictoor/WireMock which mimics the functionality from http://WireMock.org
|
|
|
|
[](https://ci.appveyor.com/project/StefH/wiremock-net)
|
|
|
|
[](https://www.nuget.org/packages/WireMock.Net)
|
|
|
|
Based on class HttpListener from the .net framework, it is very lightweight and have no external dependencies.
|
|
|
|
## Stubbing
|
|
A core feature of WireMock is the ability to return canned HTTP responses for requests matching criteria, see [Wiki : Stubbing](https://github.com/StefH/WireMock.Net/wiki/Stubbing).
|
|
|
|
|
|
## Using WireMock 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).
|
|
|
|
### SSL
|
|
You can start a standalone mock server listening for HTTPS requests. To do so, there is just a flag to set when creating the server:
|
|
```csharp
|
|
var server = FluentMockServer.Start(port: 8443, ssl: true);
|
|
```
|
|
Obviously you need a certificate registered on your box, properly associated with your application and the port number that will be used. This is not really specific to WireMock, not very straightforward and hence the following stackoverflow thread might come handy: [Httplistener with https support](http://stackoverflow.com/questions/11403333/httplistener-with-https-support)
|
|
|
|
## Simulating faults
|
|
Currently not done - need to get rid of HttpListener and use lower level TcpListener in order to be able to implement this properly
|