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,
VLS,
Please be more precise with what is not identified that you expected to be identified. The steps provided disable TestAdvantage and only change record/replay for a Microsoft button to test a specific issue.
Hi,
Even I'm facing a issue around customer application hang with QTP 11 and TestAdvantage 2010 vol3. Tried the above option mentioned but when i change the SwfConfig.xml my scripts are not identifying the objects.
Please advice.
THanks
VLS
Chandan,I would like you to test record and playback on your application using the attached custom server for a Microsoft Button. This will determine if the issue is due to using any custom replay server or if it is specific to TestAdvantage.To test this you will need to modify the SwfConfig.xml file to point to the record and replay server and then simply record the same actions in your application. When replaying the script, see if the remoting call still hangs your application and let me know the results.Steps to update the SwfConfig.xml:1. Extract ButtonTest.zip to C:\ (This creates a ButtonTest folder)2. Create a backup of your SwfConfig.xml file (C:\Program Files\HP\QuickTest Professional\dat\SwfConfig.xml)3. Remove all of the mappings for record/replay servers from the SwfConfig.xml file. When done, you should have a file with the following content:<?xml version="1.0" encoding="UTF-8"?><Controls></Controls>4. Open the Configuration.xml file from the attached zip file (C:\ButtonTest\Configuration.xml)5. Copy all of the contents of Configuration.xml and paste them between the opening and closing Controls tags in the SwfConfig.xml filePlease note that the if you choose to use a directory other than C:\ to extract the test record and replay assembly to, the Configuration.xml file will need to be updated to match the location where you have extracted ButtonTest.zip. The ButtonTest.zip file also contains the code for the custom server in the code folder. Once you have tested this, you will want to restore your SwfConfig.xml file from the back up you have made.When you have completed the test, let me know if this hung your application like TestAdvantage does. Alan
If I disable the add-in, record and reply the steps, the application is NOT hanging.
But when I disable the add-in, SetCell data does NOT work. Only ActivateCell works and it does NOT serve the purpose as it is just clicking on the cell, irrespective of whether the checkbox is checked or NOT.
Cheers,
Thank you for the additional information. I once come across an issue with remoting and QTP hanging. This issue was only reproducible in the customers application and would happen when any custom replay servers were used.
As such, I would like to know what happens if TestAdvantage is disabled. To test this, please use the Version Utility to set TestAdvantage to be disabled and then record clicking the CheckBox in the grid and the button that does the remoting call.
Once you have done the recording, playback the script. Does QTP still hang or does the call work without issue? Let me know the results so that I know what the next step should be for debugging this issue.