How Auto Correlation Works

 

Basic Example

Let’s there be a Alpha request/response Pair such that

Copy 
request(Alpha) = http://server/getProducts
response(Alpha) = [{productId=512,productName=“Screw”, price= “5”},
{productId=631,productName=“Hammer”, price= “10.4”} ]

And let Beta be a request/response Pair such that

Copy 
request(Beta) = http://server/purchaseProduct?id=512
response(Beta) = …

A correlation could be seen here in the productId from the request of Alpha which is used in the response of Beta. Highlighting the correlation.

Copy 
response(A) = [{productId=512,productName=“Screw”, price= “5”},
{productId=631,productName=“Hammer”, price= “10.4”} ]
request(B) = http://server/purchaseProduct?id=512

Supported Formats

  • HTML

  • XML

  • JSON

  • CSV

Features and Best Practices

  • When working with autocorrelation, Always check to Execute all HAR calls (even after a failure) in the Options panel of Scenario Builder under HAR Script Options.

  • Never check 'Mark each request as a step' (it will make autocorrelation fail sometimes).

  • Autocorrelation rejects unnecessary correlations.

  • Autocorrelation makes har scripts Less brittle.

  • Autocorrelation cleans duplicated correlations.

  • A1 -- > B

    A2 -- > C

    A1 == A2

    Automatically transform A2 to A1 (Shrinks memory footprint)

    A1 -- > B

    A1 -- > C

  • 'Show headers, requests, and responses in each test case execution output' option is useful for the Development team to debug, similar to the designer script debug option. Please mark this option if (and only if) you want the development team to review autocorrelation.

  • Autocorrelation supports URLs with or without port, the below 2 URLs are handled the same way.

    • https://appvance.ci.cloudbees.com/login.html

    • https://appvance.ci.cloudbees.com:443/login.html