@ -147,6 +147,15 @@ public class WebClientDataBufferAllocatingTests extends AbstractDataBufferAlloca
@@ -147,6 +147,15 @@ public class WebClientDataBufferAllocatingTests extends AbstractDataBufferAlloca
<4> Manually perform an ASYNC dispatch (as there is no running container)
<5> Verify the final response
Registered filters are invoked through the `MockFilterChain` from `spring-test`, and the
last filter delegates to the `DispatcherServlet`.
====
[[spring-mvc-test-vs-streaming-response]]
@ -5108,13 +5131,31 @@ with `WebTestClient`. One extra advantage is the ability to use the `StepVerifie
@@ -5108,13 +5131,31 @@ with `WebTestClient`. One extra advantage is the ability to use the `StepVerifie
project Reactor that allows declaring expectations on a stream of data.
[[spring-mvc-test-server-filters]]
===== Filter Registrations
When setting up a `MockMvc` instance, you can register one or more Servlet `Filter`
===== Differences Between Out-of-Container and End-to-End Integration Tests
===== Spring MVC Test vs End-to-End Tests
As mentioned earlier Spring MVC Test is built on the Servlet API mock objects from the
`spring-test` module and does not use a running Servlet container. Therefore, there are
some important differences compared to full end-to-end integration tests with an actual
client and server running.
Spring MVC Test is built on Servlet API mock implementations from the
`spring-test` module and does not rely on a running container. Therefore, there are
some differences when compared to full end-to-end integration tests with an actual
client and a live server running.
The easiest way to think about this is by starting with a blank `MockHttpServletRequest`.
Whatever you add to it is what the request becomes. Things that may catch you by surprise
@ -5155,7 +5196,7 @@ important thing to check. In short, there is room here for multiple styles and s
@@ -5155,7 +5196,7 @@ important thing to check. In short, there is room here for multiple styles and s