UFT 12 is unreliable
I was wondering if anyone else out there was enduring the nightmare that is UFT 12. We are having so many issues with this and their support seems unable to even understand the issues.
- Dynamically loading qfl files freezes UFT - Support unable to reproduce even though we can 100%. They cant do anything about this.
- Breakpoints being skipped. Even though this is a known issue with a patch it still skips breakpoints
- Syntax issue encountered during run time can lead to HRESULT E_Fail has been returned from a call to a COM component even though I am not doing any COM calls.
Support seems to be completely unprepared to resolve any issues. They don't even really know what UFT is. We cant seem to get to someone that actually can do anything about the problems. Its so frustrating. Support calls just go in circles.
We found the only 'solution' to the dynamically loading QFL files issue is to rebuild the system so that it has never seen HP products before. The lengthy manual efforts that HP sends you through don't work. I cant believe they manually make you do that rather than have that included as part of their installer. Clearly customer's time is not valuable to HP.
Last edited by DarrenMartin; 03-02-2015 at 07:51 AM.
UFT 12.02 patch to fix UFT ignoring breakpoints does help prevent lockups but there are still plenty of breakpoints being skipped. HPs understanding of what run to cursor or stop over means differs from the industry standard. Those ignore breakpoints thus making the entire point of having a breakpoint useless - you will need to manually navigate to it rather than count on UFT to make your development experience efficient.
I do not know if it is a feature or defect. The scirpt remembers breakpoints from the previous time that the scirpt was opened.
Does any else notice this?
Generally I think it's good to run any automation tool under a VM. That way you can have your SUT and UFT setup under a clean VM so none of that 3rd party interference. Then when you need troubleshooting, you can send that entire VM to their lv 3 support for more technical troubleshooting.
Originally Posted by DarrenMartin
The Script remembers the breakpoins, it's the known issue in UFT 11.53 inorder to overcome this after completing of script exceution remove all the breakpoints by Ctrl+shift+f9, most of the cases it works...
IF you are running v12 on VMs I would advise upgrading to the latest version as we consistently saw memory leaks with v12 on Windows-7 VMs.
I have also seen this. Frustrating, though at least these a local settings, no something that will be experience by someone else opening the same test on another box. In fact, it seems these can be cleared by brute force by deleting all files from C:\Users\<User Id>\AppData\Local\HP\UFT\Preferences\, except for RecordWindowPersistenceProperties.xml and RunWindowPersistenceProperties.xml. However, generally seems better to simply be sure to clear all breakpoints manually via UI.
Originally Posted by bklabel1
Regarding MISSING breakpoints, this is something I've never encountered. You mention "run to cursor" v "stop over". What are your understandings of these terms and their differences, and what are you seeing in UFT?
The most bizarre events regarding unreliability I've witnessed since upgrading to v12 is in version control. I've often seen lines of code change when a check out is done. That's right: you have some test, all you do is a check out, and a section of code is replaced with code from another version. Scary! Has anyone seen this? I am keeping my eyes open to track this issue, and will post more details if I can narrow down the symptoms/cause.
Oh, really? Which version control tool and what version are you using?
Originally Posted by cqao
When you say "section of code is replaced with code from another version", do you mean a line or two or more lines of code and from what other version (last one changed, second to the last, or a version from last year)?
This will be good to know so others can be aware.
I've upgraded (with A LOT of hesitation) from QTP11 to QFT12.02.
Since then... I've had major problems that HP can not resolve.... I've lost days working with their support, to no avail.
My biggest problem is the performance of the tool when it comes to opening tests AND most of all is the huge memory leaks that cause all sorts of errors/crashes...
Reliability... Browser syncs don;t always work... I'm not sure why.
For your breakpoints issue, try re-installing the ms script debugger from microsoft's website.
Tags for this Thread