From c3987c41af0f5e1ba0719cbe2b61a66579e5e702 Mon Sep 17 00:00:00 2001 From: Stef Heyenrath Date: Mon, 21 Dec 2020 13:52:24 +0100 Subject: [PATCH] Updated Using WireMock in UnitTests (markdown) --- Using-WireMock-in-UnitTests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Using-WireMock-in-UnitTests.md b/Using-WireMock-in-UnitTests.md index 5cd1d80..0b505fa 100644 --- a/Using-WireMock-in-UnitTests.md +++ b/Using-WireMock-in-UnitTests.md @@ -1,6 +1,6 @@ # WireMock with your favorite UnitTest framework -Obviously you can use your favourite test framework and use WireMock within your tests. In order to avoid flaky tests you should: - - let WireMock choose dynamicaly ports. It might seem common sens, avoid hard coded ports in your tests! +Obviously you can use your favorite test framework and use WireMock.Net within your tests. In order to avoid flaky tests you should: + - let WireMock.Net choose ports dynamically . It might seem common sense, avoid hard coded ports in your tests! - clean up the request log or shutdown the server at the end of each test Below a simple example using Nunit and NFluent test assertion library: