Blog

Let’s say you are testing a web application and the service level agreement of response times for each web page is 1.5 seconds or below. You might want to automatically fail any transaction that comes back in a longer amount of time. You will need to measure the number of milliseconds in the transaction, and see exceeds this amount. You might need to set something like this up for any transaction where timing for milliseconds is crucial. Just because the business process passes, does not mean the transaction should pass, especially Read Entire Entry

Let’s say you want to capture the http response of a page, but it redirects you (code 302). The normal way you might capture the HTTP status code is capturing it in a variable:
HttpRetCode = web_get_int_property(HTTP_INFO_RETURN_CODE);
This would be put after the page request in the script. However, this will only capture the LAST status code received. If there is a redirection in between, it will not be captured. So how do you get the first one? Capture the response header using a correlation. Use the web_reg_save_param function Read Entire Entry

Note: This article was originally posted on Loadtester.com, and has been migrated to the Northway web site to maintain the content online.
Citrix applications represent the second most common protocol for LoadRunner engagements at Loadtester Incorporated Northway Solutions Group. Our white paper from 2006 on Citrix best practices continues to be a very popular download on the site. In 2008, we’ve presented this information to the Citrix iForum and at local user groups. There continues to be a lot of interest in testing Citrix Read Entire Entry