Hello Khan,
we have a similar test environment setup - TestExecute is installed on a remote machine and runs independently and without user interaction.
Our idea was to be able to start the test in the afternoon or evening hours and let the tests run during the night without monitoring.
So we ended up with the follwing:
- the machine where TestExecute is installed and running is available via RDP (A)
- the RDP to machine A is opened from any other machine (B) -> machine B must be running 24/7.
- on the machine B (where RDP to A is opened from) a registry setting must be made to support minimized desktop:
HKEYLOCALMACHINE
-> SOFTWARE
-> Microsoft
-> Terminal Server Client -> RemoteDesktop_SuppressWhenMinimized = 2 (DWORD)
In this scenario user connects via RDP from machine B to machine A and starts the test project run in TestExecute.
Then he minimizes the RDP window on machine B - thus having the RDP in the task bar.
We actually use RDP also to the machine B from any local machine (e.g. test engineers or other staff in charge):
- RDP from any local machine to machine B
- RDP from B to A
- start test on A
- minimize RDP on B
- close RDP to B on local machine (closing via "X", not logging off)
- power off local machine
This way user can start the test execution, power off his local machine and leave his desk after COB wihout having to monitor the process.
Hope this helps,
Marin
