No it's in single script mode. It also does not pause when pause is pressed. It needs
L-CTRL 3 to stop it. Usually it reaches an error first though as something is missing, like GUI, or it starts halfway through a function, wherever the arrow happens to be at the time.
Nope, we run the scripts both from TD and within WR. When run from TD we set them to local. It happens most when writing scripts, swapping windows etc. Could there be some undocumented softkeys that I'm hitting to make it run?
"Problem Description: The test script runs on its own or the test results randomly appear
The user has found that WinRunner will randomly run a script or pop-up the test results. This occurs when WinRunner is up in the background but not in use.
Diagnosis: This can be caused by the following:
The keyboard/mouse driver for the system is not a standard keyboard driver. This problem is often seen when the driver is a Logitech driver.
The softkeys for your application overlap with the defined softkeys for WinRunner.
A virus scanner or another application is interacting with WinRunner unexpectedly.
Solution: Use the standard keyboard driver
Reboot the machine. If the problem continues, check the keyboard/mouse driver. If it is not a standard driver, change it to the standard "pc/at enhanced keyboard101/102 key (from Microsoft)" driver.
If you are using a standard keyboard/mouse driver, check the defined softkey values. If WinRunner and your application both use the same softkeys, WinRunner may respond when you use them with your application. For information on how to update WinRunner's softkeys, refer to Problem ID 12270 - How to enable, disable, or modify WinRunner's hotkeys\softkeys
If the keyboard/mouse driver is a standard driver and WinRunner's softkeys do not overlap with those of your application, check for other applications or processes that may be running in the background. Close any applications and terminate any processes that are not needed."
It's not too late to be what you might have been. - Penguin Wisdom
I had a funny similar experience with a Mercury supporter last month. I had made everything ready for a webex session with him and WinRunner stood in the middle of a long script where my problems was. The webex opened another browser window and suddenly the script began to run. I too could not break it and at the end my script closed all open browser windows as it should. And bang! the webex session was closed too. He had a lot of patience and we had to start again.
[This message has been edited by zelm (edited 02-21-2003).]
Test thatrun without being started is a known symptom since WR 7.0 for users who use non generic mouse drivers especially Logitech drivers.
It is recommended that you install the regular MS drivers for your mouse. It should fix it.
If it's working... don't touch it!