WireMock.Net.AspNetCore.Middleware 1.6.4-preview-01

Prefix Reserved
.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher.
This is a prerelease version of WireMock.Net.AspNetCore.Middleware.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package WireMock.Net.AspNetCore.Middleware --version 1.6.4-preview-01                

                    
                

            
NuGet\Install-Package WireMock.Net.AspNetCore.Middleware -Version 1.6.4-preview-01
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="WireMock.Net.AspNetCore.Middleware" Version="1.6.4-preview-01" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add WireMock.Net.AspNetCore.Middleware --version 1.6.4-preview-01                

                    
                

            
#r "nuget: WireMock.Net.AspNetCore.Middleware, 1.6.4-preview-01"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install WireMock.Net.AspNetCore.Middleware as a Cake Addin
#addin nuget:?package=WireMock.Net.AspNetCore.Middleware&version=1.6.4-preview-01&prerelease

// Install WireMock.Net.AspNetCore.Middleware as a Cake Tool
#tool nuget:?package=WireMock.Net.AspNetCore.Middleware&version=1.6.4-preview-01&prerelease

WireMock.Net

Lightweight Http Mocking Server for .NET, inspired by WireMock.org (from the Java landscape).

⭐ Key Features

  • HTTP response stubbing, matchable on URL/Path, headers, cookies and body content patterns
  • Library can be used in unit tests and integration tests
  • Runs as a standalone process, as windows service, as Azure/IIS or as docker
  • Configurable via a fluent C# .NET API, JSON files and JSON over HTTP
  • Record/playback of stubs (proxying)
  • Per-request conditional proxying
  • Stateful behaviour simulation
  • Response templating / transformation using Handlebars and extensions
  • Can be used locally or in CI/CD scenarios
  • Can be used for Aspire Distributed Application testing

⭐ Stubbing

A core feature of WireMock.Net is the ability to return predefined HTTP responses for requests matching criteria. See Wiki : Stubbing.

⭐ Request Matching

WireMock.Net support advanced request-matching logic, see Wiki : Request Matching.

⭐ Response Templating

The response which is returned WireMock.Net can be changed using templating. This is described here Wiki : Response Templating.

⭐ Admin API Reference

The WireMock admin API provides functionality to define the mappings via a http interface see Wiki : Admin API Reference.

⭐ Using

WireMock.Net can be used in several ways:

UnitTesting

You can use your favorite test framework and use WireMock within your tests, see Wiki : UnitTesting.

Unit/Integration Testing using Testcontainers.DotNet

See Wiki : WireMock.Net.Testcontainers on how to build a WireMock.Net Docker container which can be used in Unit/Integration testing.

Unit/Integration Testing using an an Aspire Distributed Application

See Wiki : WireMock.Net.Aspire on how to use WireMock.Net as an Aspire Hosted application to do Unit/Integration testing.

As a dotnet tool

It's simple to install WireMock.Net as (global) dotnet tool, see Wiki : dotnet tool.

As standalone process / console application

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

As a Windows Service

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

As a Web Job in Azure or application in IIS

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

In a docker container

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

HTTPS / SSL

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

📚 Documentation

For more info, see also this WIKI page: What is WireMock.Net.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.6.8 76 11/24/2024
1.6.7 98 10/17/2024
1.6.7-preview-02 84 10/6/2024
1.6.7-preview-01 83 10/2/2024
1.6.6 97 10/1/2024
1.6.5 85 9/28/2024
1.6.4-preview-01 75 9/28/2024

# 1.6.4 (25 September 2024)
- #1169 Allow mapping without Path or Url [bug]
- #1170 Update the .NET Aspire tests [feature]
- #1172 Fix JSON parsing of text/plain content type [bug]
- #1177 Unpin Testcontainers version and upgrade to version 3.10.0 [bug]
- #1178 Upgrade CS-Script to version 4.8.17 [feature]
- #1179 Add WireMock.Net.TUnit project [feature]
- #1146 Bump Request CS-Script 4.8.13 to 4.8.17 [feature]
- #1167 Admin API fails to create a mapping with Request Header matching using WildCardMatcher [bug]
- #1168 Numbers in text/plain content is parsed as JSON. [bug]
- #1176 WireMock.NET TestContainer Dependency Constraint Issue [bug]

The full release notes can be found here: https://github.com/WireMock-Net/WireMock.Net/blob/master/CHANGELOG.md