Spring启动REST应用程序测试方法

Question

I have a Spring boot + REST application. When I need to write unit testing, should I directly invoke the service beans or call the rest controller? If I invoke the rest controller directly, I have to use RestTemplate and invoke the rest api as a client, right?

What would be the best and required practice?

If I invoke the service beans directly it will result in less code coverage because controller methods code will be not covered. Is that acceptable?

Answer 1

Hmm, this is a complex question but I'll answer as best I can. A lot of this will depend on you/your organization's risk tolerance and how much time they want to invest in tests. I believe in a lot of testing, but there is such a thing as too much.

A unit test tests the unit of code. Great, but what's a unit? This article is a pretty good discussion: http://martinfowler.com/bliki/UnitTest.html but a unit is basically the smallest testable part of your application.

Much literature (eg https://www.amazon.ca/Continuous-Delivery-Reliable-Deployment-Automation/dp/0321601912/ ) describes multiple phases of testing including unit tests which are very low level and mock externalities such as DBs or file systems or remote systems, and "api acceptance tests" (sometimes called integration tests although this is a vague term that can mean other things). This latter type fires up a test instance of your application, invokes APIs and asserts on responses.

The short answer is as follows: for unit tests, focus on the units (probably services or more granular), but the other set of tests you describe, wherein the test behaves like a client and invokes your api, are worthwhile too. My suggestion: do both, but don't call both unit tests.

Answer 2

Best Approach is to Test VIA Controllers. WebServices are entered and values are returned here. So Controller is having quite a good role in this. There can be small logic as well, you may miss that

You can Try Using the MockMvc Method for testing controllers.

Reference: Reference-1 , Reference-2

Or use the RestTemplate as you mentioned in question Reference-3

Answer 3

它基于您想要测试的内容，您可以分离您的测试，特别是如果您有开发人员团队，测试用例来测试您的业务“服务”，另一个测试用例作为集成测试来使用REST模板，在这种情况下你可以更快更容易地找出你的错误。

Answer 4

It depends on what you want to do.

One approach would be to unit test the units of work, like the service and the MVC controller. These test will only test eventual logic found in this classes and try to reach a high branch coverage, if applicable. Besides this, you can write an integration test that makes the HTTP request, goes to the real service bean and only mock an eventual resource access.

For integration tests you can use Spring's support, see here: http://docs.spring.io/spring/docs/current/spring-framework-reference/html/integration-testing.html#spring-mvc-test-framework