Running WireMock.Net without starting a server

[Code-Grump]

Is there a way to run WireMock.Net without starting a server instance running on a physical port? It would be great to be able to create a server-less instance that exposes an HttpMessageHandler or HttpClient in a similar fashion to ASP.NET's TestServer. It would be easy to inject these properties into a system-under-test to avoid having to go over a physical network link.

[StefH]

@Tragedian
I see your point, however WireMock.Net is created specifically (at this moment) to mock the wire and the requests and responses and can be used to mock 3rd party services.

[Code-Grump]

I can see that the implementation is currently built around middleware configured using WebHostBuilder. That makes it a relatively simple job to add the middleware to a TestServer instance. Perhaps WireMockServer could be extended in some fashion to support any server capable of hosting the middleware?

[StefH]

Maybe making WireMockMiddleware public will already solve your question?

[Code-Grump]

It would be a fantastic step in that direction, certainly. The only challenge then would be configuring the middleware options, as those methods all exist on the server, not the options themselves. It probably wouldn't be hard to move some logic around to achieve that though.

[StefH]

The middle ware depends on:

• IWireMockMiddlewareOptions options
• IOwinRequestMapper requestMapper
• IOwinResponseMapper responseMapper
• IMappingMatcher mappingMatcher

However code to add/configure mappings is not working because these methods are defined on the WireMock server code.

[StefH]

Closing...