We've got a number of scripts that were originally created in QTP 8.2 that we recently updated to QTP 9.2 (basically just opening the 8.2 version using QTP 9.2 and saving a new copy with a slightly different name). Whether that's really what the issue is here, I can't say for sure, but it may be a factor in it.
These scripts may take from several minutes to several hours to run to completion, with the results normally being written to the Quality Center (which, incidently, still stands at version 8.2), but somewhere in the middle of some of the longer ones, they are intermittantly going to sleep. It's like QTP loses it's place and when we go back to check on the progress of the test, the script will be displayed, starting with line number one at the top of the screen, sometimes with the execution pointer at line number one, sometime with no pointer visible at all and "running" flashing in the status tray. Also, because of the state that it leaves the application being tested, we can tell that it never happens at the same spot in the script twice. It could doze off anywhere in the script randomly.
Any attempts to abort the script fail, no variables will display and any commands entered return an ambiguous "<Unexpected>" error message. The only course of action at that point is to end-task the process and start over again. Of course, the end-task keeps any results from being written also.
Anyone have this happening to them? Or does anyone have any ideas on how to resolve this issue?
These scripts may take from several minutes to several hours to run to completion, with the results normally being written to the Quality Center (which, incidently, still stands at version 8.2), but somewhere in the middle of some of the longer ones, they are intermittantly going to sleep. It's like QTP loses it's place and when we go back to check on the progress of the test, the script will be displayed, starting with line number one at the top of the screen, sometimes with the execution pointer at line number one, sometime with no pointer visible at all and "running" flashing in the status tray. Also, because of the state that it leaves the application being tested, we can tell that it never happens at the same spot in the script twice. It could doze off anywhere in the script randomly.
Any attempts to abort the script fail, no variables will display and any commands entered return an ambiguous "<Unexpected>" error message. The only course of action at that point is to end-task the process and start over again. Of course, the end-task keeps any results from being written also.
Anyone have this happening to them? Or does anyone have any ideas on how to resolve this issue?
