Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #16718 from Tetsuya3850

Browse Source 
* pr/16718:
  Polish "Document the pros and cons of MockMvc"
  Document the pros and cons of MockMvc

Closes gh-16718
This commit is contained in:
Phillip Webb
2019-09-03 21:04:22 -07:00
parent 827c624b22 624c118cdf
commit da1d7cff14
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View File

@@ -5639,6 +5639,16 @@ Alternatively, you can configure a {spring-framework-docs}testing.html#webtestcl
include::{code-examples}/test/web/MockWebTestClientExampleTests.java[tag=test-mock-web-test-client]
----
[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 on lower level Servlet concerns 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.
If you need to tests these lower-level concerns, you can start a fully running server as described in the next section.
====
[[boot-features-testing-spring-boot-applications-testing-with-running-server]]