(Using RDP only works as long as the RDP client is logged in and its window is not minimized. No logins via Remote Desktop (RDP) are made. Power save mode is disabled (no turning off the screen, no suspend to ram or suspend to disk). (After locking the desktop test scripts hang and time out.) (Enabled and active screen saver causes test scripts to hang and time out.)ĭesktop is not locked.
(That is, start it yourself in cmd.exe for example.) Squishserver is not running as a Windows service, and it is not being started from a Windows service. Run test scripts as the currently logged in user on Windows. There is only one solution unfortunately, and it consists of meeting all of the following requirements: Maybe it's stuck in an endless loop? Solutions ¶ The AUT '' did not respond to network communication. One symptom for these test script execution problems is the following error message in the log: The basic problem is that if the GUI of the application cannot be drawn, then its objects do not have coordinates on the screen, and so Squish cannot find out where to perform a mouse click, for example. There are several situations in which test scripts will hang and time out on Windows.Īll of these revolve around the availability (or lack thereof) of a "screen" to draw/paint the application on.
0 kommentar(er)
