关于Spring MVC测试API的model().attribute()方法的询问

Question

我正在尝试使用Spring MVC测试API测试以下控制器方法：

@RequestMapping(value = "/preference/email", method = RequestMethod.GET, produces = "text/html")
public String emailForm(@ModelAttribute EmailInfo emailInfo, Model model, @CurrentMember Member member) {
    emailInfo.setEmail(member.getEmail());
    emailInfo.setActivated(member.isActivated());
    emailInfo.setToken(member.getToken());
    model.addAttribute("emailInfo", emailInfo);
    return "preference";
}

当我调试以下测试方法时...

@Test
    public void shouldPopulateEmailInfo() throws Exception {
        when(currentMemberHandlerMethodArgumentResolver.supportsParameter(any(MethodParameter.class))).thenReturn(Boolean.TRUE);
        when(currentMemberHandlerMethodArgumentResolver.resolveArgument(any(MethodParameter.class), any(ModelAndViewContainer.class), any(NativeWebRequest.class), any(WebDataBinderFactory.class))).thenReturn(currentMember);
        mockMvc.perform(get("/preference/email"))//
                .andDo(print())//
                .andExpect(model().attribute("emailInfo.email", "[e-mail]"));//
    }

。我确实看到"[e-mail]"设置在电子邮件信息的电子邮件字段中。

但是，我系统地得到：

java.lang.AssertionError: Model attribute 'emailInfo.email' expected:<[e-mail]> but was:<null>
    at org.springframework.test.util.AssertionErrors.fail(AssertionErrors.java:60)
    at org.springframework.test.util.AssertionErrors.assertEquals(AssertionErrors.java:89)
    at org.springframework.test.web.servlet.result.ModelResultMatchers$2.match(ModelResultMatchers.java:68)
    at org.springframework.test.web.servlet.MockMvc$1.andExpect(MockMvc.java:141)
    at com.bignibou.tests.controller.preference.PreferenceControllerEmailManagementTest.shouldPopulateEmailInfo(PreferenceControllerEmailManagementTest.java:109)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
    at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
    at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
    at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
    at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

有些东西我没有从Spring Mvc测试API中得到......谁能帮忙？

编辑：这是我在考虑提供的答案后得出的

：

.andExpect(model().attribute("emailInfo", Matchers.hasProperty("email", Matchers.equalTo("[e-mail]"))));//

它现在工作正常。

Answer 1

正如Sotirios指出的那样，model().attribute("attributeName")不允许你导航，它会使用整个东西作为名称。

但是，您可以改用此方法：

public <T> ResultMatcher attribute(final String name, final Matcher<T> matcher)

这将允许您指定一个 Hamcrest 匹配器来匹配您的属性，例如：

.andExpect(model().attribute("emailInfo", hasProperty("email", is("[e-mail]"))))

只要确保类路径中有 Hamcrest 库，然后像这样导入它：

import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.*

注意：如果您使用 Groovy 进行测试 （Spock），导入尤其重要，因为 Hamcrest 中的方法名称与 Groovy 标准库冲突

Answer 2

Model属性是字符串键对象值对。没有表达式解析正在进行。当你这样做时

model().attribute("emailInfo.email", "[e-mail]"));//

您询问是否存在具有指定值的键emailInfo.email的 Model 属性。答案显然是否定的，因为您没有具有此类键的Model属性。

你拥有的是

model.addAttribute("emailInfo", emailInfo);

这是一个具有键emailInfo的Model属性，用于保存类型为 EmailInfo 的对象。您需要自己比较EmailInfo对象的email字段。