Introduce JsonPath matchers for empty and non-empty content [SPR-13352]

[spring-projects-issues]

Sam Brannen opened SPR-13352 and commented

This issue picks up where #17935 left off.

---

Affects: 3.2 GA

Issue Links:

• JsonPath assertions fail to differentiate between definite and indefinite results in checks for existence [SPR-13351] #17935 JsonPath assertions fail to differentiate between definite and indefinite results in checks for existence ("depends on")
• Introduce additional JsonPath matchers in Spring MVC Test [SPR-13320] #17905 Introduce additional JsonPath matchers in Spring MVC Test
• Why MockMvcResultMatchers has not a xpath method with org.hamcrest.Matcher<T>? [SPR-13687] #18262 Why MockMvcResultMatchers has not a xpath method with org.hamcrest.Matcher?

Referenced from: commits 7a17abe

[spring-projects-issues]

Sam Brannen commented

Implemented in GitHub commit 7a17abe:

Introduce empty & non-empty JsonPath matchers

This commit introduces new isEmpty() and isNotEmpty() methods in JsonPathResultMatchers and JsonPathRequestMatchers which delegate to the new assertValueIsEmpty() and assertValueIsNotEmpty() methods in JsonPathExpectationsHelper, respectively.