You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2021/08/29 09:20:33 UTC
[Bug 65299] JSONPathAssertion attributes are out of order
https://bz.apache.org/bugzilla/show_bug.cgi?id=65299
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FixedInTrunk
--- Comment #2 from Felix Schumacher <fe...@internetallee.de> ---
@AG, could you test the next nightly and report back, whether it fixes your
problem?
commit ee0c973bffcdce9832a3437614fab0e59ab222c4
AuthorDate: Tue May 11 18:20:13 2021 +0200
JSONPathAssertion attributes are out of order
Compare JSON objects and not their string representations.
When using our stringifier, the order of the entries in maps
is not guaranteed and can lead to wrong results.
In the old days we made no difference between a string or int
when asserting a result. Jackson JSON Parser differentiates
between 'foo' and '"foo"' (former is invalid) and '1' and '"1"'
(former is an int, latter a string).
To enable both (complex, simple and edge cases), we now have to do
more work.
Bugzilla Id: 65299
---
.../jmeter/assertions/JSONPathAssertion.java | 7 ++-
.../assertions/jmespath/JMESPathAssertion.java | 11 +++-
.../jmeter/assertions/TestJSONPathAssertion.java | 73 +++++++++++++---------
.../assertions/jmespath/TestJMESPathAssertion.java | 6 +-
xdocs/changes.xml | 2 +
5 files changed, 66 insertions(+), 33 deletions(-)
--
You are receiving this mail because:
You are the assignee for the bug.