QTP v10
TestAdvantage 2007 Volume 1 CLR 2.0 against same version of NetAdvantage
If I do a grid.SetCellData in my QTP script, it will completely lock the application under test and QTP as well, causing the application process to start consuming half the CPU consistently.
If I end the process on QTP my AUT is still running high CPU and in an unusable state, I have to forcibly kill it's process as well.
However, if I make sure that the very last line in the QTP script is SetCellData, it works fine. Only if I make any other GUI method or action call *after* the SetCellData call, will it lock up.
Hello,
With the release of HP QuickTest Professional 10, there were breaking changes in the custom server provided by HP that we derive from to create the replay servers for TestAdvantage. Due to this change, there are some cases where applications may hang including when using SetCellData. Development is working with HP to determine and resolve these issues.
As you are using TestAdvantage 2007 Volume 1 for CLR 2.0, it is recommended to use QTP 9.5 or earlier as TestAdvantage 2007 Volume 1 is no longer maintained and there won't be any updates to the code for this volume of TestAdvantage.
Let me know if you have any questions with this matter.
Alan
Hi Alan,
I'm also facing the same issue. I'm forced to use Test Advantage 2005 Volume 3 CLR 1.0 for one of our window based applications built on Net Advantage 2005. We were using QTP 9.5 earlier and just now upgraded to QTP 10.0 But the momenyt I try to do a setcelldata on the Infragistics grid and click on a button, the application is hanging. I tried to bypass the setcelldata command by using Keyboard inputs. But there seems to be something wrong happening or something that is supposed to happen but is not being simulated by QTP. I'm able to manually run the same scenario and I know this has got nothing to do with our application. Request you to help me on this.
Regards,
Chandan
Chandan,
The issue is resolved in the latest service release for TestAdvantage 2008 Volume 2 and later. For TestAdvantage 2009 Volume 2 and later this is addressed in the release version. For all versions of TestAdvantage older than TestAdvantage 2008 Volume 2, it is recommended to use an older version of QTP.
Your options are to use an older version of QTP for testing the AUT (application under test), Upgrade the AUT to use NetAdvantage 2008 Volume 2 or later so you can use TestAdvantage 2008 Volume 2 or later, or you can modify the source code yourself for the older version of TestAdvantage to resolve the issue.
Thanks a lot for the reply. I'm glad that this issue is resolved in the later version of TestAdvantage.
It has been decided that our application will be upgraded to NetAdvantage 2008. But that is not something I can wait till it happens.
When you say older version of QTP, which version do you think will not have problem? I faced this issue in QTP 9.5 and in QTP 10.0. We cannot downgrade to an older version of QTP at our firm.
You have mentioned that we can modify the source code to resolve this issue. Could you please share this info with me? I can work with the developers to make it work. Business users have been chasing me to automate this and if this quick fix works, I'll be very relieved.
Thanks and Regards,
I have created a support case for you and provided the details on how to modify the TestAdvantage source code through the case. When I say an older version of QTP I am referring to QTP 9.2 or older. I have seen cases where QTP 9.5 works and cases where it fails.