Support for JSON Format

Applies to LoadComplete 4.97, last modified on May 20, 2019

This topic describes how LoadComplete supports the JSON format.

About JSON

JSON is a format used for serializing and transmitting structured data over a network connection. It is typically used for exchanging structured data between a server and web applications.

What Does JSON Support Mean

LoadComplete can decode JSON. This means that with LoadComplete, you can perform load testing of applications that use this format for their browser-server communication. LoadComplete supports recording and playing back of JSON requests and provides you with access to individual data values that are sent to or received from the server. So, you can easily parameterize JSON requests.

Also, LoadComplete supports automatic correlation of JSON request and response data. See About Data Correlation.

To record JSON, you do not have to make any special preparations. You can record traffic in the same way as you record HTTP traffic (see Recording User Scenarios).

If you record a user scenario on a web application using the JSON format, you will see the contents of JSON requests and responses in the scenario editor:

Contents of a JSON Request

Click the image to enlarge it.

The Content-Type attribute of JSON requests is application/json:

Content-Type of a JSON Request

Parameter Attributes

For each parameter, LoadComplete displays the following information:

Column Description
Parameter The parameter name.

LoadComplete obtains the parameter name from the JSON stream. The parameters whose names LoadComplete fails to retrieve are reported as Unnamed. If there are several such parameters on the same tree level, they are reported as Unnamed (2), Unnamed (3) and so on. The index is restarted on each level.

Array items are displayed as Item[index_in_the_array], for example, Item[0], Item[1] and so on. Items of associative arrays are displayed with appropriate parameters, for instance, Item["MyAttrValue"].

Type The parameter type.
Value The parameter value as it was during the scenario recording.

If a parameter of the String type is empty, LoadComplete will not display anything in the cell.

If you see that a parameter has the String type and the Value is nil, this means that the parameter contains the string “nil”.

Variable In responses, you use variables to store parameter values that LoadComplete extracts during a test run. You can then use those values in subsequent requests.

In requests, you replace the recorded parameter value with the value of the specified variable. This can be either a value extracted from a previous response, or a value that LoadComplete generates or loads from an external file.

Path The path to the parameter in the parameter tree, starting from the root element.

You use the path to create correlation rules for parameters. See Data Correlation.

You can also use the path to create data selectors and data replacers to extract parameters from responses and to replace the recorded parameters with the needed values.

How You Parameterize JSON Requests

The key benefit of accessing data values passed in JSON streams is that you can change them in your tests. This helps you pass information from earlier requests to further requests with ease. The entire procedure is very simple:

  • Open your scenario for editing.

  • In the scenario editor, find the request that obtains data from the server.

For step-by-step information on parameterization, see Parameterizing Rich Internet Application Traffic.

Note: LoadComplete does not change the request structure. You can change parameter values, but you cannot create or delete parameters or change their type.

See Also

Supported Protocols and Data Formats
Support for Silverlight Applications
Parameterizing Rich Internet Application Traffic

Highlight search results