From 8f8a4af001176e35fbe332d2c532d400d73246a8 Mon Sep 17 00:00:00 2001 From: Tetsuya Hasegawa Date: Sun, 5 May 2019 07:20:58 +0900 Subject: [PATCH] Document the pros and cons of MockMvc Update the MockMvc documentation to provide more details about the pros and cons of such an approach, specifically calling out the difference with error page handling. See gh-16718 --- .../src/main/asciidoc/spring-boot-features.adoc | 6 ++++++ 1 file changed, 6 insertions(+) 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 e37b99a008f..53acfcf7647 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 @@ -5639,6 +5639,12 @@ Alternatively, you can configure a {spring-framework-docs}testing.html#webtestcl include::{code-examples}/test/web/MockWebTestClientExampleTests.java[tag=test-mock-web-test-client] ---- +Testing within a mocked environment enables fast runs as it does not require the cost of setting up a full Servlet container. +Although this works fine in most cases, you cannot test situations where the servlet container takes precedence. +For example, Spring Boot's error handling is based on Servlet container’s error mappings. +Therefore, exceptions behave differently in the container-less mock environment than the real environment. +If you need to test the precise format of the error response, test with a fully running server as follows. + [[boot-features-testing-spring-boot-applications-testing-with-running-server]]