Skip to content
Browse files
JSON Assertion always successful with indefinite paths
Add a note to the component reference for JSON Path Assertions

Bugzilla Id: 65794
  • Loading branch information
FSchumacher committed Jan 18, 2022
1 parent abb069c commit 6a5cac0ad75e72d5313f3c795845c6cea9ff6520
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 0 deletions.
@@ -253,6 +253,7 @@ however, the profile can't be updated while the test is running.

<li><bug>65794</bug>JSON Assertion always successful with indefinite paths</li>

@@ -300,6 +301,7 @@ however, the profile can't be updated while the test is running.
<p>We also thank bug reporters who helped us improve JMeter.</p>
<li>Nikola Aleksic (nalexic at</li>
<li>Vladimir Rosu (rosuvladimir at</li>
Apologies if we have omitted anyone else.
@@ -5035,6 +5035,9 @@ please ensure that you select "<code>Store the message using MIME (raw)</code>"
Second, it will search for specified path, using syntax from <a href="" >Jayway JsonPath 1.2.0</a>. If the path is not found, it will fail.
Third, if JSON path was found in the document, and validation against expected value was requested, it will perform validation. For the <code>null</code> value there is special checkbox in the GUI.
Note that if the path will return array object, it will be iterated and if expected value is found, the assertion will succeed. To validate empty array use <code>[]</code> string. Also, if patch will return dictionary object, it will be converted to string before comparison.
<note>When using <a href="">indefinite JSON Paths</a>
you must assert the value due to the existing JSON library implementation, otherwise the assertion could always
return successful</note>

0 comments on commit 6a5cac0

Please sign in to comment.