JSON Matchers does not offer "Click to see difference"
See original GitHub issueWhen using a JSON matcher and the assertion fails, there is no “Click to see difference” option in IntelliJ to quickly compare them.
Working example:
401 shouldBe 402
JSON Example:
"""{"a":1}""" shouldMatchJson """{"a":2}"""
This is very useful when comparing larger JSON objects.
Comparing the output, it looks like the JSON example values need to be wrapped in <X>
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Testing two JSON objects for equality ignoring child order in ...
This method is not symmetric, as it only tests 'subset' relationship of the children, not equality. the 'other' object may have more children...
Read more >JSONPath Match Assertion | ReadyAPI Documentation
The JSONPath Match assertion uses a JSONPath expression to select content from the target property and compare the result to the value you...
Read more >Karate API Automation-Assertions using matcher APIs - Medium
In this post, I would be covering following topics related to Payload Assertions: Assert whole actual JSON against expected JSON using match ......
Read more >Tasks in Visual Studio Code
Any background/watch tasks used in dependsOn with "dependsOrder": "sequence" must have a problem matcher that tracks when they are "done". The following task ......
Read more >Setting the AWS CLI output format - AWS Documentation
For more advanced filtering that you might not be able to do with --query , you can consider jq , a command line...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m not sure what kind of changes warrants a cherry-picked 4.7 release at this point. 5.0 is honestly not that far away from what I can tell, unless JetBrains run into issues with shipping Kotlin 1.6. I guess it’s up to @sksamuel 🙂
See the milestone issue, all tagged issues are done.
I see what I did wrong… new fix OTW 😃