Java 弹簧控制器捕捉块中的单元测试代码
我有以下结构的控制器：Java 弹簧控制器捕捉块中的单元测试代码,java,spring,unit-testing,junit,mockito,Java,Spring,Unit Testing,Junit,Mockito,我有以下结构的控制器： @RequestMapping(value = "${foo.controller.requestMappingUrl.login}", method = RequestMethod.POST) public ResponseMessage<String> loginUser( @RequestParam("username") String username, HttpServletRequest httpServletReq
@RequestMapping(value = "${foo.controller.requestMappingUrl.login}", method = RequestMethod.POST)
public ResponseMessage<String> loginUser(
@RequestParam("username") String username, HttpServletRequest httpServletRequest,
HttpServletResponse httpServletResponse) {
try {
return fooService.login(username); // can mock test
} catch (UserNotFoundException e) {
//CANNOT MOCK TEST THIS BLOCK
String errorMsg = LoggerUtil.printStackTrace(e);
LOG.error("[RequestId: {}] UserNotFoundException: {}, Stack: {}", requestId, e.getMessage(), errorMsg);
httpServletResponse.setStatus(HttpStatus.NOT_ACCEPTABLE.value());
statusCode = StatusCode.UserNotFound.value();
responseMessage.buildResponseMessage(StringUtils.EMPTY, HttpStatus.NOT_ACCEPTABLE, statusCode,
messageByLocaleService.getMessageResponse(statusCode, null, locale));
}
}
你能发布fooService.login的内容吗？对不起，cmmiiw，既然我在模拟服务层，为什么你需要服务层代码呢。服务层函数使用Atlassian crowd并抛出从群组api返回的UserNotFoundException。请发布您得到的NestedServletException的测试代码和堆栈跟踪。@nanospeck然后发布您对该功能的模拟代码使用模拟和堆栈跟踪更新问题您可以发布fooService.login？对不起，cmmiiw，既然我在模仿服务层，为什么你需要服务层代码呢。服务层函数使用Atlassian crowd并抛出从群组api返回的UserNotFoundException。请发布您得到的NestedServletException的测试代码和stacktrace。@nanospeck然后发布您模拟此功能的代码使用mocking和stack tracehey更新问题，听起来是个不错的选择。但是我如何处理编译器警告，在控制器类中用try/catch块包围服务方法。不要在控制器中捕获它，而是在控制器方法签名中添加throws子句，这样ControllerAdvice就会小心了！糟糕的是，我在测试类中模拟了名称重复的错误异常，调用了“import com.atlassian.crowd.Exception.runtime.UserNotFoundException”而不是“import com.atlassian.crowd.Exception.UserNotFoundException”。接受这个答案是因为我发现这种优雅的实现方式有助于尽早识别错误，从而避免了我的错误。我在这里写了一个简单的例子：嘿，听起来是个不错的选择。但是我如何处理编译器警告，在控制器类中用try/catch块包围服务方法。不要在控制器中捕获它，而是在控制器方法签名中添加throws子句，这样ControllerAdvice就会小心了！糟糕的是，我在测试类中模拟了名称重复的错误异常，调用了“import com.atlassian.crowd.Exception.runtime.UserNotFoundException”而不是“import com.atlassian.crowd.Exception.UserNotFoundException”。接受这个答案是因为我发现这种优雅的实现方式有助于尽早识别错误，从而避免了我的错误。我在这里写了一个简单的示例：
@SuppressWarnings("unchecked")
@Test(expected = UserNotFoundException.class)
public void testControllerUserNotFoundException() throws Exception {
Response resp = new Response();
resp.setStatusCode(StatusCode.UserNotFoundErrorCode);
when(fooService.login(any(String.class)).thenThrow(UserNotFoundException.class);
mockMvc.perform(post("/service-user/1.0/auth/login?&username=test")
.contentType(contentType)).andExpect(status().isNotAcceptable())
.andExpect(jsonPath("$.statusCode", is("ERRORCODE144")));
}
@ControllerAdvice
public class ExceptionControllerAdvice {
@ExceptionHandler(UserNotFoundException.class)
public ResponseEntity<String> handleUnexpectedException(UnexpectedException
unExpectedExe) {
//log and send the response back to the client here
}
}
@RequestMapping(value = "${foo.controller.requestMappingUrl.login}",
method = RequestMethod.POST)
public ResponseMessage<String> loginUser(
@RequestParam("username") String username,
HttpServletRequest httpServletRequest,
HttpServletResponse httpServletResponse) {
return fooService.login(username);
}
@Before
public void setUp() throws Exception {
MockitoAnnotations.initMocks(this);
mockMvc = MockMvcBuilders.standaloneSetup(projectController)
.setMessageConverters(new MappingJackson2HttpMessageConverter())
.setControllerAdvice(new ExceptionControllerAdvice()).build();
}
@SuppressWarnings("unchecked")
@Test
public void testControllerUserNotFoundException() throws Exception {
Response resp = new Response();
resp.setStatusCode(StatusCode.UserNotFoundErrorCode);
when(fooService.login(any(String.class)).
thenThrow(UserNotFoundException.class);
mockMvc.perform(post("/service-user/1.0/auth/login?&username=test")
.contentType(contentType)).
andExpect(status().isNotAcceptable())
.andExpect(jsonPath("$.statusCode", is("ERRORCODE144")));
}