Use below command to get name and image: kubectl get pods -Ao jsonpath=”{range .items[*]}{@.metadata.name}{” “}{@.spec.template.spec.containers[].image}{“\n”}{end}” It will give output like below: name image
How about adding several andExpect methods? Something similar to: mockMvc.perform(get(“https://stackoverflow.com/”)).andDo(print()).andExpect(status().isOk()) .andExpect(jsonPath(“$.links[0].rel[0]”, is(“self”))) .andExpect(jsonPath(“$.links[0].href[0]”, is(“https://stackoverflow.com/”));
SelectToken(“data[0].user_id”) doesn’t work because there isn’t an array in your JSON. You should use SelectToken(“data.user_id”) instead. Fiddle: https://dotnetfiddle.net/K0X4ht
It seems that support for returning the length() of an array was only added in version 2.1.0 of the jayway json-path library. Based on some quick tests, the $.orders.length() expression seems to work with both version 2.1.0 and version 2.2.0, so I think you just need to upgrade your dependency version in order to fix … Read more
1) Instead of .andExpect(jsonPath(“$.data.roles.length”).value(correctRoles.size())); try .andExpect(jsonPath(“$.data.roles.length()”).value(correctRoles.size())); or .andExpect((jsonPath(“$.data.roles”, Matchers.hasSize(size)))); 2) Instead of for (AuthorityRole role : correctRoles) // doesn’t work actions.andExpect(jsonPath(“$.data.roles[?(@==’%s’)]”, role.toString()).exists()); try actions.andExpect((jsonPath(“$.data.roles”, Matchers.containsInAnyOrder(“role1”, “role2”, “role3”)))); Keep in mind that you have to add hamcrest-library.
I think you need to pass the Matcher to the jsonPath method. For example. .andExpect(jsonPath(“$.version”, is(“0.1”))) References: http://docs.spring.io/spring/docs/3.2.x/javadoc-api/org/springframework/test/web/servlet/result/MockMvcResultMatchers.html#jsonPath(java.lang.String,%20org.hamcrest.Matcher) Integration Testing of Spring MVC Applications: Write Clean Assertions with JsonPath SpringMVC/ mockMVC/ jsonpath compare list of strings
but I always get an array: That is meant to happen. As you can read in this documentation, under ‘Result’ (almost at the bottom): Please note, that the return value of jsonPath is an array, which is also a valid JSON structure. So you might want to apply jsonPath to the resulting structure again or … Read more
Your query looks fine, and your data and query work for me using this JsonPath parser. Also see the example queries on that page for more predicate examples. The testing tool that you’re using seems faulty. Even the examples from the JsonPath site are returning incorrect results: e.g., given: { “store”: { “book”: [ { … Read more