单元测试的意义
以前的公司里面前后端都是自己开发的(前端为传统的jsp),测试起来很方遍,自己把项目启动本地就可以进行e2e测试了,可是后来到了现在的这家公司,项目体量很大,虽然后端也可以本地运行起来利用swagger进行接口测试,但是规定UT不能低于85% 。 刚开始觉得没有多大用处,很多的地方的UT只是为了应付code review。 慢慢的就会发现UT的居多好处,此处仅写下自己的一些感悟,详细的好处可以自行的baidu/google.
- UT相当于白盒测试,可以判断自己代码的逻辑是否符合自己的意愿, 发现最基本的逻辑错误
- 当代码中的UT覆盖率很高,考虑到的场景很全面的时候,后面的人在改代码的时候,就能够清楚的知道原因或发现修改的风险了
- 足够多的UT也能对后来人了解业务有很好的帮助作用
TestNg + Mock
整理了一下目前项目中Test模块用的相关依赖
<!-- test -->
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.powermock</groupId>
<artifactId>powermock-api-mockito</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.powermock</groupId>
<artifactId>powermock-module-testng</artifactId>
<scope>test</scope>
</dependency>
<--PODAM is a lightweight tool to auto-fill Java POJOs with data. This comes handy when developing unit tests. -->
<dependency>
<groupId>uk.co.jemos.podam</groupId>
<artifactId>podam</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
<exclusions>
<exclusion>
<artifactId>junit</artifactId>
<groupId>junit</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework.restdocs</groupId>
<artifactId>spring-restdocs-mockmvc</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>io.springfox</groupId>
<artifactId>springfox-swagger2</artifactId>
</dependency>
<dependency>
<groupId>io.springfox</groupId>
<artifactId>springfox-swagger-ui</artifactId>
</dependency>
Test For Controller
private MockMvc mockMvc;
private static final ObjectMapper OBJECT_MAPPER = new ObjectMapper();
@InjectMocks
MailTemplateController mailTemplatesController = new MailTemplateController();
@BeforeMethod
public void setUp() {
MockitoAnnotations.initMocks(this);
}
@BeforeClass
public void setup() throws IllegalAccessException {
this.mockMvc = MockMvcBuilders.standaloneSetup(mailTemplatesController).build();
}
@Test
public void testGetMailTemplates() throws Exception {
MailTemplateVOs mailTemplateVOs = getMailTemplateVOs();
when(mailTemplateService.getMailTemplates(anyLong(),anyLong(),anyString(),anyString(),anyObject(),anyString())).thenReturn(mailTemplateVOs);
MvcResult result =
this.mockMvc.perform(get("/test/mailTemplates?format=html&&hasContent=false")).andExpect(
MockMvcResultMatchers.status().isOk())
.andExpect(MockMvcResultMatchers.content().contentTypeCompatibleWith(MediaType.APPLICATION_JSON_VALUE)).andReturn();
String content = result.getResponse().getContentAsString();
JsonNode jsonNode = OBJECT_MAPPER.readTree(content);
assertEquals(jsonNode.get("items").get(0).get("id").asText(), mailTemplateVOs.getItems().get(0).getId());
}
Test For Static method
// 1. 在类上加注解
@PrepareForTest({WbxServerContext.class})
// 2. 继承PowerMockTestCase-- 具体原因后面再研究
testClass extends PowerMockTestCase
//mockito 静态方法的调用
PowerMockito.mockStatic(WbxServerContext.class);
WbxServerContextToken wbxServerContextToken = PowerMockito.mock(WbxServerContextToken.class);
PowerMockito.when(WbxServerContext.getContext()).thenReturn(wbxServerContextToken);
when(wbxServerContextToken.getSiteID()).thenReturn(1l);