QTP 11 – Recording Checkpoints Performance issue

QTP checkpoint takes looooong time to insert.

Grrr – ever try recording a QTP checkpoint only to have QTP to hang for minutes before inserting the checkpoint?

This behavior happens even when you try adding a checkpoint using the Active Screen after recording the initial script. Turns out this is a known issue with some users and the fix is to change a quick setting in QTP.

How to Fix

To fix this issue try changing the following setting in QTP:

  1. Navigate to Tools>Options>Web>Advanced

  2. Scroll down until you locate the “Learn and run using automatic XPath identifiers” and uncheck it.

  3. Click the ‘Apply’ and ‘Ok’ buttons.
  4. Close QTP and start it back up. Once it’s back up try inserting a checkpoint again. The performance issues should be fixed!

What does this setting do anyway?

If you’re wondering what this option does here is a quick explanation. This setting generates and stores XPath values when learning a Web test objects. When you run QTP it tries to use this value to improve object identification reliability. When QTP is running it uses the learned XPath value to return the DOM element from the app and verifies that this object matches the test object description. If it does not, the learned XPath is ignored. Also, if the description for a test object includes the XPath or CSS identifier, this option is ignored for that object.

That’s it hope it helps you!




Leave a comment:

1 comment
Greg Woffindin - December 30, 2014

I have a question on QTP checkpoints I was hoping you could help on. I have created a checkpoint, both standard with HTML check and a regular text checkpoint, that contains a large amount of text and in the middle is a URL that will change based on the test environment. I have tried replacing the URL with wild cards (.*) but it fails. I also tried a variable from the datatable but this also failed. Not sure what I am doing wrong, any suggestions?

Click here to add a comment

Leave a comment: