9 Frequently Faced Issues for QTP or UFT with Detailed Solutions

Introduction to Issues for QTP or UFT

In this post, I going to concentrate on the top ten frequently faced issues for QTP/UFT. Mostly we face these issues in our day-by-day testing. We google a lot and finally get the solution. I am trying to summarize them and jot them down in point by point manner.

QTP does not throw any error but can not identify the objects.

Possible Solutions:

1.Check the builds if you have picked up the correct build of the application to test. This is one of the basic issues of today’s testing process. Also, it is always better to check the QTP/UFT build number. Here is a document on how to find out build.

2. Check the Zoom level. Sometimes increasing the zoom level will solve this issue. Mostly this issue occurs when we work on the Pega application. Pega’s layered approach gets hidden when it is not 100%. Sometimes to identify an element we need to Zoom in 125%.

3. Tabbed browser is not supported. Uncheck the Tabbed browsing option so that QTP/UFT can run smoothly.

4. QTP/UFT stops just after few lines maybe 3 to 4 lines in debug mode.F10 does not move the cursor to the next line.
The best possible issue could be the lack of space in the drive where QTP/UFT is installed. Increase the space to accommodate the temp files.
Check for the RAM availability. If many processes are trying to get executed at the same time, QTP may get starvation issues.
If the above does not work out, reset the QTP/UFT to factory settings. Lastly, you can uninstall and install it freshly.

See also  How to Call Reusable API Script From GUI Script in UFT

5. Type casting error: It happens when we try to read data from the data table. It must take the parameter in a string but sometimes it fails to identify the data as a string.
Error code Error:Parameter <<VariableName>> should be srring but undefined.
Check the data table column and convertible methods. Also, check if the variable is defined or not.

Further visit: How to Work With Environment Variable in UFT?

6. Remote execution is fine and smooth so as local but even if you have good Citrix net speed and local net speed you may face slow execution issues. QTP behaves like dead slow.
Similar to point no-4, Check for RAM size and available applications running along with Citrix. Less RAM size and many parallel processes may slow down the QTP/UFT execution process.

7. Excel connectivity issue. Every time office is upgraded to 2007 to 2010 to 2013 to 2017, QTP/UFT can not read excel. It stops, hangs, freezes during execution.
The best possible way to resolve this issue is to create connectivity with excel using ADODB.
Here is a good tutorial on the same.

8.Record script does not work properly. Mostly while selecting values from dropdowns. – Try to use descriptive programming. Most of the cases get resolved by this. if this does not solve this issue. try select (1) or select(#1).

9. We have licenses across teams. The client has given us a total of 10 licenses. When our team is trying to access QTP, QTP is throwing an error saying no QTP available to use.

See also  Which is better Xpath or DOM?

This is a common issue in our team in our day-to-day use. Many of us do not shut down/close QTP to terminate the session. We just lock the Screen to go home.

This time UFT/QTP session is unused but can not be accessed.
To resolve the issue we need to use the locked concept of QTP/UFT.In that case, the licenses we will be locking will be available for our use.

Another team can use the remaining licenses(total licenses-locked licenses)
Here is a link that helps –https://community.hpe.com/t5/Unified-Functional-Testing/Locking-Code-for-QTP-QC-concurrent-licence/td-p/4488389

we can verify QTP software dump->license server -utilities ->winadmin.exe who are using the licenses.

image credit: www.information-age.com

Share and Enjoy !

Leave a Reply

Your email address will not be published. Required fields are marked *