From 14e3295b530fccb7ee79fb49fdfd76a3c2bf2eaf Mon Sep 17 00:00:00 2001 From: Stef Heyenrath Date: Mon, 21 Dec 2020 13:52:37 +0100 Subject: [PATCH] Updated Using WireMock in UnitTests (markdown) --- Using-WireMock-in-UnitTests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Using-WireMock-in-UnitTests.md b/Using-WireMock-in-UnitTests.md index 0b505fa..9dc01a1 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 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! + - let WireMock.Net choose ports dynamically. 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: