https://bz.apache.org/bugzilla/show_bug.cgi?id=65794
Bug ID: 65794
Summary: JSON Assertion always successful with filter operators
Product: JMeter
Version: 5.4.3
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.5
I'm testing an HTTP endpoint which returns the following content:
{
"isCompressed": true,
"rows": [
{
"_2": "",
"_4": "CustomString_1401",
"_5": {
"latitude": 0.0,
"longitude": 0.0,
"elevation": 0.0
},
"_6": "CustomString_1401",
"_8": "User0",
"_9": "User",
"_10": [],
"_11": 1641561103991
},
{
"_2": "",
"_4": "CustomString_3930",
"_5": {
"latitude": 0.0,
"longitude": 0.0,
"elevation": 0.0
},
"_6": "CustomString_3930",
"_8": "User0",
"_9": "User",
"_10": [],
"_11": 1641561045657
}
]
}
The following JSON assertion paths always return successful, even if those
paths do not exist.
$.rows[?(@._4=="Custom")]._4
$.rows[?(@._4=="Custom_3930")]._122
I believe this is a bug, as in case of assertion 1, there's no element which
satisfies the filter, and in case of Filter 2, there's no key whose name is
"_122".
--
You are receiving this mail because:
You are the assignee for the bug.
