Overview
- In LoadRunner 11.5, TruClient for Internet Explorer has been introduced. It is now possible to use TruClient on IE-only web applications.
Note: This still supports only HTML + JavaScript websites. It does not support ActiveX objects or Flash or Java Applets, etc.
- TruClient IE was developed as an add-in for IE 9, so it will not work on earlier versions of IE. This version of IE was the first version to expose enough of the DOM to be usable by a TruClient-style Vusers. Note that your web application must support IE9 in “standard mode”.
- Some features have also been added to TruClient Firefox. These include:
- The ability to specify think time
- The ability to set HTTP headers
- URL filters
- Event handlers, which can automatically handle intermittent pop-up windows, etc.
- Web page breakdown graphs have been added to TruClient (visible in LoadRunner Analysis). Previously they were only available for standard web Vusers.
Tips and Tricks
NTLM authentication -
Scenario: Some applications when accessed on Mozilla, demand NTLM authentication. If these steps appear while recording, they don’t get recorded. Hence while replaying, due to the absence of these steps; the application fails to perform the intended transactions.
Solution: To avoid a situation in which an application asks for NTLM authentication while recording and replaying, one has to specify the application as a trusted NTLM resource. To make that, follow these steps.
- Open the file “user.js” located in “%lr_path%\dat\LrWeb2MasterProfile”.
- Locate the preference setting “network.automatic-ntlm-auth.trusted.uris”.
- Specify the URL of the trusted resource as the value of this setting.
- Save the file “user.js”
These changes are done only where the VUgen is used to develop the script. These changes get saved with the script and apply on different machines during load tests.
