From a3cde7fd8d1664ece7ff7d71eabeb07ce29c3d28 Mon Sep 17 00:00:00 2001 From: Phillip Webb Date: Wed, 4 Sep 2019 22:20:14 -0700 Subject: [PATCH] Fix typo --- .../src/main/asciidoc/spring-boot-features.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index b8af4b54d16..6fdbca1b8cb 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -5642,7 +5642,7 @@ include::{code-examples}/test/web/MockWebTestClientExampleTests.java[tag=test-mo [TIP] ==== Testing within a mocked environment is usually faster than running with a full Servlet container. -However, since mocking occurs at the Spring MVC layer, code that relies on lower-level Servlet container behavor cannot be directly tested with MockMvc. +However, since mocking occurs at the Spring MVC layer, code that relies on lower-level Servlet container behavior cannot be directly tested with MockMvc. For example, Spring Boot's error handling is based on the "`error page`" support provided by the Servlet container. This means that, whilst you can test your MVC layer throws and handles exceptions as expected, you cannot directly test that a specific <<#boot-features-error-handling-custom-error-pages, custom error page>> is rendered.