Spring的MockMvc是用来做单元测试还是集成测试的？
Are Spring's MockMvc used for unit testing or integration testing?
Spring 有 2 个 MockMvc 设置：
- 独立设置
- WebApplicationContext 设置
一般来说，MockMvc 用于什么样的测试？单元还是集成？还是两者？
我说的是否正确，使用独立设置（运行 在 Spring 的应用程序上下文之外）允许您编写单元测试，而使用 WebApplicationContext 设置您可以编写集成测试？
我会说这两种方法都用于集成测试，但独立会强制您指定要测试的控制器。
WebApplicationContext 设置正在加载整个上下文，因此您不关心服务于例如 /people POST 请求的特定控制器在哪里。
所以我建议使用 WebApplicationContext 设置来测试您的 REST API 在应用程序需要使用的接口方面。您不会将测试与实际代码结合起来 + 您正在记录应用程序的行为方式。
这两种形式实际上都是集成测试，因为您正在测试代码与Spring DispatcherServlet 和支持基础架构的集成。区别在于幕后使用的支持基础设施的数量。
详细信息记录在 Spring 参考手册中。
值得注意的摘录：
The "webAppContextSetup" loads the actual Spring MVC configuration
resulting in a more complete integration test. Since the TestContext
framework caches the loaded Spring configuration, it helps to keep
tests running fast even as more tests get added. Furthermore, you can
inject mock services into controllers through Spring configuration, in
order to remain focused on testing the web layer.
...
The "standaloneSetup" on the other hand is a little closer to a unit
test. It tests one controller at a time, the controller can be
injected with mock dependencies manually, and it doesn’t involve
loading Spring configuration. Such tests are more focused in style and
make it easier to see which controller is being tested, whether any
specific Spring MVC configuration is required to work, and so on. The
"standaloneSetup" is also a very convenient way to write ad-hoc tests
to verify some behavior or to debug an issue.
...
Just like with integration vs unit testing, there is no right or wrong
answer. Using the "standaloneSetup" does imply the need for some
additional "webAppContextSetup" tests to verify the Spring MVC
configuration. Alternatively, you can decide to write all tests with
"webAppContextSetup" and always test against actual Spring MVC
configuration.
...
The options provided in Spring MVC Test are different stops on the
scale from classic unit to full integration tests. To be sure none of
the options in Spring MVC Test are classic unit tests but they are a
little closer to it. For example you can isolate the service layer
with mocks injected into controllers and then you’re testing the web
layer only through the DispatcherServlet and with actual Spring
configuration, just like you might test the database layer in
isolation of the layers above. Or you could be using the standalone
setup focusing on one controller at a time and manually providing the
configuration required to make it work.
如有疑问，我建议您先阅读参考手册，然后再在这里发帖提问。 ;)
此致，
Sam（Spring TestContext Framework 的作者）
Spring 有 2 个 MockMvc 设置：
- 独立设置
- WebApplicationContext 设置
一般来说，MockMvc 用于什么样的测试？单元还是集成？还是两者？
我说的是否正确，使用独立设置（运行 在 Spring 的应用程序上下文之外）允许您编写单元测试，而使用 WebApplicationContext 设置您可以编写集成测试？
我会说这两种方法都用于集成测试，但独立会强制您指定要测试的控制器。
WebApplicationContext 设置正在加载整个上下文，因此您不关心服务于例如 /people POST 请求的特定控制器在哪里。
所以我建议使用 WebApplicationContext 设置来测试您的 REST API 在应用程序需要使用的接口方面。您不会将测试与实际代码结合起来 + 您正在记录应用程序的行为方式。
这两种形式实际上都是集成测试，因为您正在测试代码与Spring DispatcherServlet 和支持基础架构的集成。区别在于幕后使用的支持基础设施的数量。
详细信息记录在 Spring 参考手册中。
值得注意的摘录：
The "webAppContextSetup" loads the actual Spring MVC configuration resulting in a more complete integration test. Since the TestContext framework caches the loaded Spring configuration, it helps to keep tests running fast even as more tests get added. Furthermore, you can inject mock services into controllers through Spring configuration, in order to remain focused on testing the web layer.
...
The "standaloneSetup" on the other hand is a little closer to a unit test. It tests one controller at a time, the controller can be injected with mock dependencies manually, and it doesn’t involve loading Spring configuration. Such tests are more focused in style and make it easier to see which controller is being tested, whether any specific Spring MVC configuration is required to work, and so on. The "standaloneSetup" is also a very convenient way to write ad-hoc tests to verify some behavior or to debug an issue.
...
Just like with integration vs unit testing, there is no right or wrong answer. Using the "standaloneSetup" does imply the need for some additional "webAppContextSetup" tests to verify the Spring MVC configuration. Alternatively, you can decide to write all tests with "webAppContextSetup" and always test against actual Spring MVC configuration.
...
The options provided in Spring MVC Test are different stops on the scale from classic unit to full integration tests. To be sure none of the options in Spring MVC Test are classic unit tests but they are a little closer to it. For example you can isolate the service layer with mocks injected into controllers and then you’re testing the web layer only through the DispatcherServlet and with actual Spring configuration, just like you might test the database layer in isolation of the layers above. Or you could be using the standalone setup focusing on one controller at a time and manually providing the configuration required to make it work.
如有疑问，我建议您先阅读参考手册，然后再在这里发帖提问。 ;)
此致，
Sam（Spring TestContext Framework 的作者）