A.: Tests that do not interact with GUI (for example, load tests) can be run on locked computers. GUI tests or tests that simulate user actions cannot be run on locked computers, since when the computer is working in this mode, the user session is frozen (no windows can be shown) and the testing engine cannot simulate user actions.
To work around the problem with tests interacting with GUI, you can use a remote desktop connection, a virtual machine or a network suite.
The Remote Desktop Connection is a built-in feature of the operating system. In order to use it, the workstation that TestComplete is running on must have special server-side software. This software may be included in the operating system, like it is included in Windows XP, or it can be a third-party software like VNC or DameWare.
TestComplete will function in the remote connection session even if the TestComplete workstation is locked. For more information on using the Remote Desktop to run tests on remote computers, see Running Tests via Remote Desktop.
When running GUI tests via Remote Desktop, do not disconnect from the Remote Desktop Connection session or lock the computer. Otherwise, the tests will fail. Also keep in mind that if you minimize the Remote Desktop window, the operating system switches the Remote Desktop session to the GUI-less mode and does not draw the GUI. In this case, TestComplete fails to interact with the GUI and the test fails.
For information on how to run GUI tests while the Remote Desktop window is minimized, see Running Tests in Minimized Remote Desktop Windows. For information on how to disconnect from the remote desktop session, see Disconnecting From Remote Desktop Session While Running Automated Tests.
To workaround the problem with a locked computer, you can also use Virtual Machine software, VMware server, VMware ESX or Microsoft Virtual server 2005:
TestComplete will run tests on the virtual machine despite the host being locked.
It is possible to run tests on locked computers using network suites; locked computers being slave hosts. However, this approach requires that TestComplete is installed on both the locked computer and the computer that will initiate the test run.
TestComplete running on the master computer will log into the locked slave computer using the specified account and run tests on that computer. Note that TestComplete does not log out from the slave computer once the tests are finished.
© 2012 SmartBear Software. All rights reserved.