我在Spring MVC中有一个带有可选路径变量的方法。我试图在没有提供可选路径变量的情况下测试它。
来自Controller的@RequestMapping(value = "/some/uri/{foo}/{bar}", method = RequestMethod.PUT)
public <T> ResponseEntity<T> someMethod(@PathVariable("foo") String foo, @PathVariable(value = "bar", required = false) String bar) {
LOGGER.info("foo: {}, bar: {}", foo, bar);
}
使用MockMvc进行测试的片段 -
//inject context
@Autowired
private WebApplicationContext webApplicationContext;
protected MockMvc mockMvc;
@Before
public void setup() {
//build mockMvc
mockMvc = MockMvcBuilders.webAppContextSetup(webApplicationContext).build();
}
@Test
public void someMethodTest() throws Exception {
//works as expected
mockMvc.perform(put("/some/uri/{foo}/{bar}", "foo", "bar"))
.andExpect(status().isOk()); //works
//following doesn't work
//pass null for optional
mockMvc.perform(put("/some/uri/{foo}/{bar}", "foo", null))
.andExpect(status().isOk()); //throws 404
//pass empty for optional
mockMvc.perform(put("/some/uri/{foo}/{bar}", "foo", ""))
.andExpect(status().isOk()); //throws 404
//remove optional from URI
mockMvc.perform(put("/some/uri/{foo}", "foo"))
.andExpect(status().isOk()); //throws 404
}
答案 0 :(得分:11)
使用像@RequestMapping
这样的数组......
@RequestMapping(value = {"/some/uri/{foo}", "/some/uri/{foo}/{bar}"}, method = RequestMethod.PUT)
public ResponseEntity<String> someMethod(@PathVariable("foo") String foo, @PathVariable(value = "bar", required = false) String bar) {
return new ResponseEntity<>(foo + " and " + (bar == null ? "<null>" : bar), HttpStatus.OK);
}
...将使此测试通过:
@Test
public void someMethodTest() throws Exception {
MvcResult mvcResult = mockMvc.perform(put("/some/uri/{foo}/{bar}", "foo", "bar"))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and bar", mvcResult.getResponse().getContentAsString());
mvcResult = mockMvc.perform(put("/some/uri/{foo}/{bar}", "foo", null))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and <null>", mvcResult.getResponse().getContentAsString());
mvcResult = mockMvc.perform(put("/some/uri/{foo}/{bar}", "foo", ""))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and <null>", mvcResult.getResponse().getContentAsString());
mvcResult = mockMvc.perform(put("/some/uri/{foo}", "foo"))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and <null>", mvcResult.getResponse().getContentAsString());
}
这当然似乎是最简单的解决方案,它可能对Swagger等工具更友好,因为它使映射显式化。
但是,您也可以声明通配符映射,然后在控制器方法中使用路径匹配器来解释请求URI。例如,这种方法......
private final AntPathMatcher antPathMatcher = new AntPathMatcher();
@RequestMapping(value = "/some/uri/with/wildcards/**", method = RequestMethod.PUT)
public ResponseEntity<String> someMethod(HttpServletRequest request) {
String matched = antPathMatcher.extractPathWithinPattern(
(String) request.getAttribute(HandlerMapping.BEST_MATCHING_PATTERN_ATTRIBUTE), request.getPathInfo());
// ugly parsing code to read the path variables, allowing for the optionality of the second one
String foo = matched;
String bar = null;
String[] pathVariables = matched.split("/");
if (pathVariables.length > 1) {
foo = pathVariables[0];
bar = pathVariables[1];
}
return new ResponseEntity<>(foo + " and " + (bar == null ? "<null>" : bar), HttpStatus.OK);
}
...将使此测试通过:
@Test
public void someMethodTestWithWildcards() throws Exception {
MvcResult mvcResult = mockMvc.perform(put("/some/uri/with/wildcards/{foo}/{bar}", "foo", "bar"))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and bar", mvcResult.getResponse().getContentAsString());
mvcResult = mockMvc.perform(put("/some/uri/with/wildcards/{foo}/{bar}", "foo", null))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and <null>", mvcResult.getResponse().getContentAsString());
mvcResult = mockMvc.perform(put("/some/uri/with/wildcards/{foo}/{bar}", "foo", ""))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and <null>", mvcResult.getResponse().getContentAsString());
mvcResult = mockMvc.perform(put("/some/uri/with/wildcards/{foo}", "foo"))
.andExpect(status().isOk()).andReturn();
Assert.assertEquals("foo and <null>", mvcResult.getResponse().getContentAsString());
}
答案 1 :(得分:0)
这很晚了,但我最近遇到了这种情况,并认为这篇文章会对其他人有所帮助。
如果使用可选的请求参数或路径变量模拟端点,则可以这样指定。
说我有一个方法,它从控制器调用的参数为m1(String param1, String param2)
。
参数2是控制器的可选参数,因此在运行时,如果未传递null,则将传递null。
如何模拟:
Mockito.when(m1(Mockito.anyString(), Mockito.eq(null)).the return(<whatever you want to return>)
在测试中使用Mockito.eq(null)
将其作为null传递给可选参数。