From 92ea3cb2351a16626dfb7d3ee0f97f1e9c0e5d8b Mon Sep 17 00:00:00 2001 From: Stef Heyenrath Date: Sat, 19 May 2018 08:45:58 +0200 Subject: [PATCH] Updated Stubbing and Request Matching (markdown) --- Stubbing-and-Request-Matching.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Stubbing-and-Request-Matching.md b/Stubbing-and-Request-Matching.md index 63ed752..c7cfb64 100644 --- a/Stubbing-and-Request-Matching.md +++ b/Stubbing-and-Request-Matching.md @@ -215,7 +215,7 @@ All of the standard helpers (template functions) provided by the C# Handlebars i `{{capitalize request.query.search}}` ## Stub priority -It is sometimes the case that you’ll want to declare two or more stub mappings that “overlap”, in that a given request would be a match for more than one of them. By default, WireMock.NET will use the most recently added matching stub to satisfy the request. However, in some cases it is useful to exert more control. +It is sometimes the case that you’ll want to declare two or more stub mappings that “overlap”, in that a given request would be a match for more than one of them. One example of this might be where you want to define a catch-all stub for any URL that doesn’t match any more specific cases. Adding a priority to a stub mapping facilitates this: