QTP 11.0 crashes while running "bigger" scenarios using TAO components
I am using the following:
ALM 11.0 patch 9
SAP TAO 3.0
All the components being used in the test scenario are stored on ALM. All data sheets are on a shared drive and in ALM as required.
When I run test scenarios where there are only a few (say 5-7) components involved, it runs fine. But when the number of TAO components are higher, say 25, it runs fine may be once but then QTP crashes (as per the error message) towards the end of the stage where it is "collecting"/"stringing" the TAO components.
Has someone seen this issue or can someone please suggest a possible cause/solution? I am attaching 2 screen shots - 1 screen shot is of the actual QTP crash error and the 2nd screen shot is when I try to debug the error and it gives a JIT debugger error.
Any help that is provided would be huge. Thanks in advance.
In this scenario it would be important to check CPU usage, memory consumption.
Debug the components to identify where exactly the problem appears (on a line of code, test object or Method, etc) helps.
Also consider that commonly these components are customized scripted elements created by SAP and QTP performance is limited on customized environments.
If you find that this or any post resolves your issue, mark it as an accepted solution.
Note: The Opinions expressed in my post are mine alone, and do not reflect the opinions of my employer. No warranties express or implied for any answered posted.
In this kind of scenarios I suggest you to check the following article to set up the right expectation and next step to move forward troubleshooting:
Document KM00319546 - What is SAP TAO and what to do when encountering problems on scripts with elements of SAP TAO? (http://support.openview.hp.com/selfsolve/document/KM00319546)
Hope this helps.
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution and give KUDOS to the author for their assistance".
Thanks! But as I said that the crash happens even before the execution actually starts in the script. It crashes while the components are being stringed together.
I did check the CPU/Memory...the memory usage does gets increased but is similar to what is seen in smaller scenarios that have worked..