Unitest Create(Post) method using mockito



给定一个具有以下createSchedules方法和该方法中使用的一堆常量的类SchedulerResource,如何使用 mockito 为createSchedules方法编写单元测试?

@PostMapping
public ResponseEntity<CustomResponse> createScheduler(@Valid @RequestBody SchedulerDTO schedulerDTO) {
if(schedulerDTO != null)
{
schedulerService.saveScheduler(schedulerDTO);
customResponse.setMessage("Schedule has been created!");
return new ResponseEntity<>(customResponse ,HttpStatus.OK);
} else {
customResponse.setMessage("Not Create!");
return new ResponseEntity<>(customResponse,HttpStatus.NOT_FOUND); 
}
}

测试类:

@Test
public void createScheduler_Success() throws Exception {
SchedulerDTO scheduler = new SchedulerDTO();
Long sId = new Long(2);
scheduler.setSchedulerId(sId);
scheduler.setLinearChannelId((long)1);
scheduler.setDurationMs((long) 5000);
scheduler.setStatus(StatusEnum.NEW);
scheduler.setStartTime("2018-03-01T05:55:25");
scheduler.setEndTime("2018-03-01T05:57:25");
when(schedulerService.saveScheduler(scheduler)).thenReturn(scheduler);
mockMvc.perform(post("/linear/api/1.0/schedules")
.contentType(MediaType.APPLICATION_JSON)
.content(asJsonString(scheduler)))
.andExpect(status().isOk())
.andExpect(jsonPath("$.message", is("Schedule has been created!")));        
}

所以可以:

if(schedulerDTO != null)
{
schedulerService.saveScheduler(schedulerDTO);
customResponse.setMessage("Schedule has been created!");
return new ResponseEntity<>(customResponse ,HttpStatus.OK);
}

但是呢:

else{
customResponse.setMessage("Not Create!");
return new ResponseEntity<>(customResponse,HttpStatus.NOT_FOUND);   
}

那么, - 我该如何为schedulerDTO == null的情况写作?

很简单:你传入 null,然后你为你的mockMvc对象写下不同的规范,比如andExpect(status().isNotFound()(或类似的东西(。

除此之外,您还可以使用verifyZeroInteractions((之类的方法来确保没有调用进入该模拟服务对象。

从这个意义上说,它与测试另一种情况没有太大区别:你退后一步,看看 else 分支中发生的所有事情,然后你想出如何观察/验证它们的方法。

最新更新