Parameters That LoadComplete Can Correlate Automatically

LoadComplete can detect and correlate dynamic parameters if –

• The parameter is contained in HTTP or WebSocket requests and responses (for example, in request URL, POST form fields, or cookie).

• The parameter has the same name and value in both the response and subsequent requests.

• The parameter that the response returns is used in at least one subsequent request in the same scenario.

For example:

• Session IDs and user IDs used to keep track of user sessions.

• ViewState and EventArgument values in ASP.NET application requests.

• Links to the assembly resources served via the WebResource.axd and ScriptResource.axd files.

• OAuth access tokens.

• Database record identifiers.

• Location of the requested resources to which the web server redirects requests.

To learn how to create data correlation rules for dynamic parameters, see Creating Data Correlation Rules Automatically.

These can be situations when LoadComplete will be able to correlate data automatically. This can happen, if –

• Dynamic parameters have different names in responses and requests.

• Dynamic parameters have the same name, but different values in responses and subsequent requests.

• Parameters reside in semantic URLs.

  For example, a web application can include dynamic parameters (like a session ID or a user ID) returned by the server to the web page’s URL:

  http://mywebsite/products/list/id314

  LoadComplete’s empirical search algorithms do not detect the dependence of semantic URLs on response data. (You still can create data correlation rules for such parameters.)

In these cases, you can correlate the dynamic parameters manually. See Correlating Dynamic Parameters Manually.

During the traffic simulation, LoadComplete waits for a server response that contains the needed correlation data until the correlation timeout period elapses. See About Data Correlation.