Configure a proxy server for connecting VuGen to a remote Git server

VuGen 12.53 supports integration with Git, enabling you to store scripts in a local or a remote Git repository. If a proxy server is needed to access the remote repository, the proxy configuration needs to be set up manually outside of VuGen using a Git command line client.

VuGen does not include a Git command line client, so it must be installed manually.

Follow the instructions below to set up a proxy server for Git:

  1. Install any Git command line client i.e. Git-SMC (the portable version will also work)
  2. Open the Git client (If you installed the Git-SMC run the git-cmd.exe)
  3. Execute the following command (replace the <proxy_server> and <port_number> with the correct values, note the two consecutive hyphens prepending the global option)
    git config –global http.proxy <proxy_server>:<port_number>
  4. To reset the proxy settings execute the following command (note the two consecutive hyphens prepending the global and unset options):
    git config –global –unset http.proxy

Select next row option is missing on parameters options

Select next row option is missing on parameters options

The "Select Next Row" option is missing on parameters options, and the object included inside this option.

The problem is with the .Net Libraries and resolution of the Forms.
This happens only with Windows 7 and LR 11.X configuration

Follow the below steps to fix this issue

1-Right click over the Desktop.
2-Select "Personalize".
3-Select "Display"
4-Select "Medium – 125%(default)"
5-Proceed with the Log off.
6-Login again and check the Vugen Parameter options.

Note: If the problem is present with display size of 125% move it to 100%

Error: unable to get local issuer certificate

Error: unable to get local issuer certificate

While using the Web protocol if the following error appears during the recording:

"[SSL:] X509 certificate error 20: unable to get local issuer certificate"

This is basically to verify if the certificate provided is valid or not.

To overcome this error message add the following step at the beginning of the script:

web_set_sockets_option("LOAD_VERIFY_FILE", "1");

Now your scripts should be working fine without any errors

Oracle ADF Application Record/Replay

Oracle ADF Application Record/Replay

Sometimes the record/replay of Oracle ADF script passes without error, but when you check at the backend you may find that nothing is getting updated.

Try the below option in order to reflect the backend update successfully.

Use Web(http/html) protocol and select recording option as below

Recording option –> Http Properties –> Advanced –> Headers –> Select "Record headers not in the list"

Graphs of Average Transaction Response Time & Percentile Transaction Time are not consistent

Graphs of Average Transaction Response Time & Percentile Transaction Time are not consistent

The Analysis graphs should be consistent. Either all graphs should have thinktime included or all graphs should not include thinktime. The graph of Average Transaction Response Time does not include thinktime whereas the graph of Percentile Transaction Time has thinktime inlcuded in it.

To fix this issue download this patch from the support website. — Patch.

Unpack it into folder where you install LR (the folder which contains bin subfolder) ie. C:\Program Files\HP\LoadRunner

This patch will solve problem with newly created sessions. The Analysis sessions that were created BEFORE applying this patch will not be affected and issue for them will remain.

So, please recreate your sessions from raw results if needed.

Alternatively, you can try the workaround given below:

Just create the .lra file from the results folder by clicking the .lrr file. We see that Percentile transaction response time has thinktime included in the transaction, whereas for the same transaction Average Response Time Graph is showing a much lower value. This is due to thinktime not being included for Average Response Time graph.

Create the Analysis file (*.lra file) from the .lrr file by clicking on it and do the following:

View -> Set Filter/Group by -> Click on the right side of Think Time,

You will get a pull down menu, choose include Think time. In the original graph of Average Transaction Response time, think time was not included.

Once think time is included, you will see for transactions the average response is about the same value as Percentile transaction response time .

The two graphs are now comparable.

Web Tours page with LoadRunner/Performance Center 11 is not showing the full contents

Web Tours page with LoadRunner/Performance Center 11 is not showing the full contents

If you are just getting the title but not the rest of the contents of Web Tours Page this could happen after you put in LoadRunner/Stand Alone Critical Patch 2.

Install Critical Patch 3 which will resolve this issue and you will be able to get the full contents of the Web Tours

Packages needed for HP Diagnostics integration with LoadRunner or Performance Center

Packages needed for HP Diagnostics integration with LoadRunner or Performance Center

This topic will explain what files/installers are needed for the integration between LoadRunner or Performance Center and HP .NET/J2EE Diagnostics?

Where can the LR Diagnostics "Add-In" be found?

The information given below is specific to Diagnostics 9.02 but the procedure is the same for other Diagnostics versions.

To integrate Diagnostics with LoadRunner (LR) / Performance Center (PC), you will need the LR Diagnostics Add-in Package on the LR or PC side — it’s located in the Diag Server 9.02.02 DIAGSRV_00047 installation package which is provided in the Diagnostics Server patch


On the LoadRunner or PC 11 system, unzip you got from the above "Diagnostics Server" patch installer. Then run setup.exe from the LR_AddIn directory to install the Add-In.

To determine which Diagnostics versions are compatible with specific LoadRunner and PC versions

In addition to the LR Add-in for LR or PC, you will need to have HP Diagnostics servers/mediators/probes installed and working correctly prior to using the Diagnostics metrics in LR/PC.