No detailed message when comparison of JSONString fails #101

Activity

1. vkorobkov commented on Jun 19, 2018

   

   vkorobkov

   on Jun 19, 2018

   Author

   More actions

   I found a temporary dirty workaround for Spring + MockMvc + Groovy kind of tests:

   1. Extend ResultActions with a custom matcher using groovy extension methods

   static ResultActions andExpectJson(ResultActions resultAction, Object expectedObject) {
           def expected = new ObjectMapper().writeValueAsString(body: expectedObject)
           resultAction
               .andExpect(content().contentType(MediaType.APPLICATION_JSON_UTF8))
               // todo: .andExpect(content().json(json)) when see https://github.com/skyscreamer/JSONassert/issues/101 is done
               .andExpect({ MvcResult result ->
                   def actual = result.response.contentAsString
                   JSONAssert.assertEquals(expected, """{ "body": $actual }""", true)
               })
       }

   This matcher adds a dummy root element("body") for expected/actual JSON, so these are not JSONStrings anymore.

   2. And the tests look like

   mockMvc
     .perform(request)
     .andExpect(status().isOk())
     .andExpectJson(RegisterByEmail.Result.OK) // calls my custom matcher

   Test output became a little more readable:
   
2. ericssy

   added a commit that references this issue on Dec 9, 2021

   fix issue skyscreamer#101

   6ddd2b3