From 8d959492e0ba96932e1a22a57457897045fbe4eb Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Sun, 3 May 2020 09:35:27 -0500
Subject: [PATCH] Test middleware topic

Organizational nit
---
 aspnetcore/fundamentals/middleware/index.md |  4 +-
 aspnetcore/fundamentals/middleware/write.md |  3 +-
 aspnetcore/test/middleware.md               | 79 +++++++++++++++++++++
 3 files changed, 84 insertions(+), 2 deletions(-)
 create mode 100644 aspnetcore/test/middleware.md

diff --git a/aspnetcore/fundamentals/middleware/index.md b/aspnetcore/fundamentals/middleware/index.md
index eadeec08b5a5..45b1621ddd6c 100644
--- a/aspnetcore/fundamentals/middleware/index.md
+++ b/aspnetcore/fundamentals/middleware/index.md
@@ -5,7 +5,7 @@ description: Learn about ASP.NET Core middleware and the request pipeline.
 monikerRange: '>= aspnetcore-2.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/06/2020
+ms.date: 05/03/2020
 uid: fundamentals/middleware/index
 ---
 # ASP.NET Core Middleware
@@ -255,6 +255,7 @@ ASP.NET Core ships with the following middleware components. The *Order* column
 ## Additional resources
 
 * <xref:fundamentals/middleware/write>
+* <xref:test/middleware>
 * <xref:migration/http-modules>
 * <xref:fundamentals/startup>
 * <xref:fundamentals/request-features>
@@ -458,6 +459,7 @@ ASP.NET Core ships with the following middleware components. The *Order* column
 ## Additional resources
 
 * <xref:fundamentals/middleware/write>
+* <xref:test/middleware>
 * <xref:migration/http-modules>
 * <xref:fundamentals/startup>
 * <xref:fundamentals/request-features>
diff --git a/aspnetcore/fundamentals/middleware/write.md b/aspnetcore/fundamentals/middleware/write.md
index eea831746398..3482d10614e9 100644
--- a/aspnetcore/fundamentals/middleware/write.md
+++ b/aspnetcore/fundamentals/middleware/write.md
@@ -5,7 +5,7 @@ description: Learn how to write custom ASP.NET Core middleware.
 monikerRange: '>= aspnetcore-2.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 08/22/2019
+ms.date: 05/03/2020
 uid: fundamentals/middleware/write
 ---
 # Write custom ASP.NET Core middleware
@@ -79,6 +79,7 @@ The following code calls the middleware from `Startup.Configure`:
 ## Additional resources
 
 * <xref:fundamentals/middleware/index>
+* <xref:test/middleware>
 * <xref:migration/http-modules>
 * <xref:fundamentals/startup>
 * <xref:fundamentals/request-features>
diff --git a/aspnetcore/test/middleware.md b/aspnetcore/test/middleware.md
new file mode 100644
index 000000000000..27ad2fd081c8
--- /dev/null
+++ b/aspnetcore/test/middleware.md
@@ -0,0 +1,79 @@
+---
+title: Test ASP.NET Core middleware
+author: cross
+description: Learn how to test ASP.NET Core middleware with TestServer.
+ms.author: riande
+ms.custom: mvc
+ms.date: 4/05/2019
+no-loc: [Blazor, "Identity", "Let's Encrypt", Razor, SignalR]
+uid: test/middleware
+---
+# Test ASP.NET Core middleware
+
+By [Chris Ross](https://github.com/Tratcher)
+
+Middleware can be tested in isolation using the <xref:Microsoft.AspNetCore.TestHost.TestServer>. Instantiate an app pipeline containing only the components that you need to test and send custom requests to verify middleware behavior.
+
+The requests:
+
+* Are sent in-memory rather than being serialized over the network.
+* Avoid additional concerns like port management and HTTPS certificates.
+
+Exceptions in the middleware can flow directly back to the calling test.
+
+Set up your test app, add your own middleware and services, and send a request using <xref:System.Net.Http.HttpClient>:
+
+```csharp
+[Fact]
+public async Task GenericCreateAndStartHost_GetTestServer()
+{
+    using var host = await new HostBuilder()
+        .ConfigureWebHost(webBuilder =>
+        {
+            webBuilder
+                .UseTestServer()
+                .Configure(app => { });
+        })
+        .StartAsync();
+
+    var response = await host.GetTestServer().CreateClient().GetAsync("/");
+
+    Assert.Equal(HttpStatusCode.NotFound, response.StatusCode);
+}
+```
+
+A test app can also send a request using [SendAsync(Action\<HttpContext>, CancellationToken)](xref:Microsoft.AspNetCore.TestHost.TestServer.SendAsync%2A):
+
+```csharp
+[Fact]
+public async Task ExpectedValuesAreAvailable()
+{
+    var builder = new WebHostBuilder().Configure(app => { });
+    var server = new TestServer(builder);
+    server.BaseAddress = new Uri("https://example.com/A/Path/");
+
+    var context = await server.SendAsync(c =>
+    {
+        c.Request.Method = HttpMethods.Post;
+        c.Request.Path = "/and/file.txt";
+        c.Request.QueryString = new QueryString("?and=query");
+    });
+
+    Assert.True(context.RequestAborted.CanBeCanceled);
+    Assert.Equal(HttpProtocol.Http11, context.Request.Protocol);
+    Assert.Equal("POST", context.Request.Method);
+    Assert.Equal("https", context.Request.Scheme);
+    Assert.Equal("example.com", context.Request.Host.Value);
+    Assert.Equal("/A/Path", context.Request.PathBase.Value);
+    Assert.Equal("/and/file.txt", context.Request.Path.Value);
+    Assert.Equal("?and=query", context.Request.QueryString.Value);
+    Assert.NotNull(context.Request.Body);
+    Assert.NotNull(context.Request.Headers);
+    Assert.NotNull(context.Response.Headers);
+    Assert.NotNull(context.Response.Body);
+    Assert.Equal(404, context.Response.StatusCode);
+    Assert.Null(context.Features.Get<IHttpResponseFeature>().ReasonPhrase);
+}
+```
+
+`SendAsync` permits direct configuration of an <xref:Microsoft.AspNetCore.Http.HttpContext> object rather than using the `HttpClient` abstractions. Use `SendAsync` to manipulate structures only available on the server, such as [HttpContext.Items](xref:Microsoft.AspNetCore.Http.HttpContext.Items) or [HttpContext.Features](xref:Microsoft.AspNetCore.Http.HttpContext.Features).