https://bz.apache.org/bugzilla/show_bug.cgi?id=65053

            Bug ID: 65053
           Summary: JSONPath Tester doesn't work for some expressions due
                    to updated json-path-2.5.0.jar
           Product: JMeter
           Version: Nightly (Please specify date)
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: nale...@gmail.com
  Target Milestone: JMETER 5.4.1

Hello,

Updated json-path-2.5.0.jar in latest nightly is not executing some json path
expressions:

$.store.book[?(@.price>=8 && @.category=~ /.*reference.*/)] OK
$.store.book[?(@.price>=8 || @.category=~ /.*reference.*/)] OK
$.store.book[?(@.category=~ /.*reference.*/ && @.price>=8)] doesn't work
$.store.book[?(@.category=~ /.*reference.*/ || @.price>=8)] doesn't work
$.store.book[?(@.category=~ /.*reference.*/ && @.price=~/-.+/)] doesn't work
$.store.book[?(@.category=~ /.*reference.*/ || @.price=~/-.+/)] doesn't work

Example JSON can be found here:
https://github.com/json-path/JsonPath#path-examples

Error in JSONPath Tester in VRT is "Exception: Expected character: )" and when
test is executed "ERROR o.a.j.e.j.j.JSONPostProcessor: Error processing JSON
content in JSON Extractor, message: Expected character: )"

One of my tests relies on two regexes like $.store.book[?(@.category=~
/.*reference.*/ && @.price=~/-.+/)] so extractions that were OK in 5.3, in
newest nightly are failing. If two regexes are a must, there is no workaround I
guess. Please consider reverting to json-path-2.4.0.jar until the issue is
resolved.

Someone already reported it - https://github.com/json-path/JsonPath/issues/658

P.S. Nice to see Jayway JsonPath project gets revived after few years of
inactivity. Looking forward to seeing the resolution of
https://github.com/json-path/JsonPath/issues/287 :)

Jmeter 5.3
Jmeter 5.4.1 c990226
Microsoft Windows 10 Enterprise 64-bit
java version "14.0.1" 2020-04-14

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to