During some time-consuming operations (like regression testing, for example), it may be preferable, for security purposes, to start the test run and lock the computer.
You can run tests that do not interact with GUI on locked computers. However, tests that interact with the user interface cannot run on locked computers, because, in this mode, the user session is frozen (no windows can be shown).
To work around this problem, you can —
Use Remote Desktop ConnectionsUse Remote Desktop Connections
-
Lock a computer where you will run tests.
-
Log in to the computer via the remote desktop connection from another computer.
-
Start running tests.
Tests will run in the remote session even if the computer is locked. See About Running Tests via Remote Desktop.
| Note: | To keep the remote desktop session in GUI mode so that tests could interact with applications, do not minimize the Remote Desktop window or disconnect from the session. |
Use Virtual Computers
-
Install TestComplete/TestExecute/TestLeft and your application on a virtual computer.
Copy your tests and all files, which your application and tests may require for running and testing, to the virtual computer.
-
Lock the virtual computer’s host computer.
-
Log in to the virtual computer from any other computer.
-
Start running tests.
Automated tests will run on the virtual machine despite the host being locked.
 |
To keep a user session on a virtual computer in GUI mode so that the tests could interact with tested applications, do not disconnect from the virtual computer. |