Spring 使用弹簧&x27;在MockMvc框架中,如何测试java.util.Map模型属性的大小?

Spring 使用弹簧&x27;在MockMvc框架中,如何测试java.util.Map模型属性的大小?,spring,dictionary,junit,hamcrest,mockmvc,Spring,Dictionary,Junit,Hamcrest,Mockmvc,我使用的是Spring3.2.11.RELEASE、JUnit4.11和Mockito1.9.5。使用Spring的MockMvc框架,如何在模型中测试地图的大小?我正在尝试下面的方法 mockMvc.perform(get("/admin/path/to/page") .param(“param1”, param12)) .andExpect(status().isOk())

我使用的是Spring3.2.11.RELEASE、JUnit4.11和Mockito1.9.5。使用Spring的MockMvc框架,如何在模型中测试地图的大小?我正在尝试下面的方法

    mockMvc.perform(get("/admin/path/to/page") 
                    .param(“param1”, param12))
                    .andExpect(status().isOk())
                    .andExpect(model().attribute("myMap", hasSize(1)))
但是我得到了结果异常

java.lang.AssertionError: Model attribute 'myMap'
Expected: a collection with size <1>
     but: was <{key1=org.mainco.subco.myproject.domain.MyprojectMyDto@724a133d}>
    at org.springframework.test.util.MatcherAssertionErrors.assertThat(MatcherAssertionErrors.java:76)
    at org.springframework.test.web.servlet.result.ModelResultMatchers$1.match(ModelResultMatchers.java:56)
    at org.springframework.test.web.servlet.MockMvc$1.andExpect(MockMvc.java:148)
    at org.mainco.subco.sbadmin.controllers.ContractsController2IT.testGetUpdateDistrictInfoLinkedTomyproject(ContractsController2IT.java:234)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    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.powermock.modules.junit4.rule.PowerMockStatement.evaluate(PowerMockRule.java:63)
    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:290)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
    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:363)
    at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

但我在最后一行“找不到符号”中遇到了编译错误。在Spring的mockMVC中使用这个匹配器的正确方法是什么

Hamcrest 2.0(Maven坐标:
org.Hamcrest:java Hamcrest:2.0.0.0
)有一个
isMapWithSize
匹配器。如果您使用Hamcrest 1.3,那么您必须自己创建这样一个匹配器。看看。

Hamcrest 2.0(Maven坐标:
org.Hamcrest:java Hamcrest:2.0.0.0
)有一个
isMapWithSize
匹配器。如果您使用Hamcrest 1.3,那么您必须自己创建这样一个匹配器。看看。

Hamcrest中没有地图匹配器。hasSizematcher。我的问题不是这种方法是否存在,而是如何使用mockMvc框架验证模型中地图的大小是一个特定值。如果您想让我进一步澄清,请告诉我。Hamcrest中没有地图的
hasSize
matcher。我的问题不是是否存在这样的方法,而是如何使用mockMvc框架验证我模型中地图的大小是否是一个特定值。如果您希望我进一步澄清,请告诉我。您好,当我尝试您的建议时(在成功导入库之后),我遇到了一个编译错误。请查看我的编辑。@Dave Try
org.hamcrest.collection.IsMapWithSize.aMapWithSize(3)
Hi,我在尝试您的建议(成功导入库后)时遇到了一个编译错误。请查看我的编辑。@Dave Try
org.hamcrest.collection.IsMapWithSize.aMapWithSize(3)
    mockMvc.perform(get(“/mypath”) 
                    .param(“myparam”, param1))
                    .andExpect(status().isOk())
                    .andExpect(model().attribute(“myMapModelName”, org.hamcrest.collection.IsMapWithSize(3)))