Browse Source
Prior to this commit, if a value existed at the specified JSON path but had an incompatible type, the AssertionError thrown contained a message stating that the value did not exist (i.e., "No Value at JSON Path"), which was not only misleading but also technically incorrect. This commit fixes the error message for such use cases. For example, the AssertionError thrown in such use cases now resembles the following. At JSON path "$.name", value <Lisa> of type <java.lang.String> cannot be converted to type <byte[]> Closes gh-25480pull/25798/head
Sam Brannen
4 years ago
2 changed files with 23 additions and 6 deletions
Loading…
Reference in new issue