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

            Bug ID: 65269
           Summary: JSON Extractor and JSON JMESPath Extractor Apply to
                    doesn't work as expected
           Product: JMeter
           Version: Nightly (Please specify date)
          Hardware: PC
            Status: NEW
          Severity: major
          Priority: P2
         Component: Main
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: JMETER_5.5

Created attachment 37834
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37834&action=edit
extractor wrong behavior

Hello,

In the attached test plan, there are Boundary Extractor, JSON Extractor and
JSON JMESPath Extractor. Apply to options "MainSampleAndSubSamples",
"MainSampleOnly" and "SubSamplesOnly" are used and extraction is done on
"JSR223 Sampler - create JSON response" and its subsample that is created using
JSR223 PP. The First 3 extractors of every kind are extracting values from
"JSR223 Sampler - create JSON response" and another 3 from its subsample. The
behavior of Boundary Extractor, JSON Extractor and JSON JMESPath Extractor is
not the same. Please run the test and check Debug Sampler in VRT. Boundary
Extractor works as expected but JSON Extractor and JSON JMESPath Extractor
don't. Please refer to the attached image to see what is correct and what is
wrong behavior.

P.S. Boundary extractor throws WARN message in logs if there is no match
between boundaries.

WARN o.a.j.e.BoundaryExtractor: Boundary Extractor -
BEcategoryFieldSubSamplesOnly: Error while generating result.
java.lang.IllegalArgumentException: bound must be positive
WARN o.a.j.e.BoundaryExtractor: Boundary Extractor -
BEticker_langMainSampleOnly: Error while generating result.
java.lang.IllegalArgumentException: bound must be positive

Is this expected? IMO, it should be hidden like for other extractors.

Jmeter 5.5 08c3c59
Microsoft Windows 10 Enterprise 64-bit
java version "15.0.1" 2020-10-20

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

Reply via email to