Subscribe the QA and Software Testing Newsletter FREE!! Comments Feed

Software Test Management and Planning

Friday, October 30, 2009


In my various posts in this web log, I wrote about common and important Software Testing Types, Methods and Strategies. Below are these topics. Although this is not a complete list, but soon it will increase in size as well as in quality.

Here is the list:

License Errors in HP Mercury's LoadRunner

Wednesday, October 21, 2009

License – Expired: Your LoadRunner license has expired. Please contact customer support to renew it. You have a time-limited license for your LoadRunner application. Some or all of your license features have expired.

Today, I’m going add one more tutorial in the LoadRunner section. Below are some useful tips to replay a HP Mercury's LoadRunner script for Citrix protocol while doing performance testing:

For LoadRunner 7.51 and later, users can correlate the dynamic value for a Winsock script from VuGen's Tree View. Below is further information on how it can be accomplished.

In continuation to my previous post “Recording Problems in Load Runner”, here, I’m going to give you some good and useful tips for doing recording in Load Runner.

  1. Use the mouse and not the keyboard: In LoadRunner, it is preferable to click on an object with the mouse rather then using the keyboard. During recording, use only GUI objects that are within the browser's pane. Do not use any browser icons, controls, the Stop button, or menu items, such as View > Refresh. You may, however, use the Refresh, Home, Back and Forward buttons and the address bar.
  2. Do not record over an existing script : It is best to record into a newly created script—not an existing one.
  3. Avoid context menus: Avoid using context menus during recording. Context menus are menus which pop up when clicking an item in a graphical user interface, such as right-click menus.
  4. Avoid working in a browser while recording: During recording, do not work in any browser window other than the browser windows opened by VuGen.
  5. Wait for downloads: Wait for all downloads to complete before doing any action, such as clicking on a button or filling in a text field.
  6. Wait for pages to load: During recording, it is best to wait for the page to load completely before doing the next step. If you did not wait for all of the pages to load, record the script again.
  7. Navigate to start page: If the last page in an action does not contain the links and buttons that were available at the start of the iteration, then the next iteration will fail. For example, if the first page has a text link Book A Flight, make sure to navigate to the appropriate page at the end of your recording, so that the same link will be visible at the end of the business process.
  8. Use a higher event configuration level: Record the business process again the High Event Configuration level.
  9. Disable socket level recording: In certain cases, the capturing of the socket level messages disrupts the application. For most recordings, socket level data is not required. To prevent the recording of socket level data, disable the option in the recording options. For more information, see the section about recording with Click and Script.
  10. Enable the record rendering-related property values: If the client-side scripts of the application use a lot of styling activities, enable the Record rendering-related property values option before recording the script. For example, enable this option to record additional DOM objects such as offsetTop. Note that enabling this option may decrease the replay speed. To enable record rendering-related property values in Load Runner:
  11. Open the Recording Options. Select Tools > Recording Options and select the GUI Properties:Advanced node

    Also See: Other LoadRunner Tutorials

Here, I’m going to describe some common recording problems / issues of Load Runner and how to resolve them. Normally, these problems are faced by everyone. I would request you all that leave your comments for the problems you face and how you tackle them.

  1. Firefox is not supported: Only Internet Explorer is supported for Web (Click and Script). To record browser activity on Firefox, use the Web (HTTP/HTML) protocol.
  2. Application behaves differently while being recorded: If your application behaves differently during recording, than it does without recording, you should determine if the recording problem is unique to Web (Click and Script). The effect may be that a Web page will not load, part of the content is missing, a popup window does not open, and so forth. Create a new Web (HTTP/HTML) script and repeat the recording. In the event that the recording is OK in Web (HTTP/HTML), we recommend that you disable socket level recording. The problem may be the result of an event listener. Use trial and error to disable event listeners in the Web Event Configuration Recording Options, and then re-record your session as a Web (Click and Script) user. To disable an event listener:
    • Open the Recording Options. Select Tools > Recording Options and select the GUI Properties:Web Event Configuration node.
    • Click Custom Settings and expand the Web Objects node. Select an object.
    • Select Disabled from the list in the Record column for the relevant Web object. If the recording still does not work, enable the listener you previously disabled, and try disabling another one. Repeat these steps until your recording succeeds.
  3. Dynamic menu navigation was not recorded: A dynamic menu is a menu that dynamically changes depending on where you select it. If the dynamic menu navigation was not recorded, record again using "high" event configuration mode. To set the configuration level to high:
    • Open the Recording Options. Select Tools > Recording Options and select the GUI Properties:Web Event Configuration node.
    • Move the slider to High.
  4. Certain user actions were not recorded: Check if there is a Java applet running inside the browser. If not, record the script with the Web (HTTP/HTML) protocol.
Also See: Other LoadRunner Tutorials

Search within more than 200 pages


Subscribe to our updates

Enter your email address:

Delivered by FeedBurner

Follow Software Testing Stuff on Twitter Subscribe Software Testing & QA Pages Through RSS

Blog Archive