From 8b2f276d6c2b0999fb2927fa0d272d1a0d3df283 Mon Sep 17 00:00:00 2001
From: Miguel Veloso <mvelosop@gmail.com>
Date: Wed, 11 Sep 2019 16:05:34 +0100
Subject: [PATCH] Reference unit testing with HttpClient issue

---
 Unit-and-integration-testing.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Unit-and-integration-testing.md b/Unit-and-integration-testing.md
index 67ca538..41d5afa 100644
--- a/Unit-and-integration-testing.md
+++ b/Unit-and-integration-testing.md
@@ -7,6 +7,7 @@ Tests are an excellent way to explore the internals of any application, besides
   - [Running Functional/Integration Tests](#running-functionalintegration-tests)
 - [Global integration tests across microservices](#global-integration-tests-across-microservices)
 - [Load Testing](#load-testing)
+- [Additional resources](#additional-resources)
 
 The tests in eShopOnContainers are structured in the following structure, per type:
 
@@ -109,3 +110,7 @@ Then, making sure that you have the infrastructure containers up and running (th
 
 Load Testing for eShopOnContainers is described in the [Load testing](Load-testing) page
 
+## Additional resources
+
+- **Testability issue - Approach to unit testing with `HttpClient`** \
+  <https://github.com/dotnet/docs/issues/10309#issuecomment-527249102>