In Distributed Testing, verify will not connect to slave
(This is already logged on the forum at Smartbear.com, but I thought I'd log it here too for response from a wider audience)
I am trying to setup Distributed Testing and so have added detail in the Hosts section of Network Suite.
When I try to verify the connection, I get a message including “Verification failed… The user … is not logged in on the slave computer”.
The details entered into Host are all correct.
I have worked through the checks on the “Message – Verification Failed” section of the TestComplete Help.
The same details will launch and allow use of a Remote Desktop connection between the Master machine and the Slave.
If I alter the details (user/password) to something NOT correct, I get a different message so that confirms that the details used are correct.
I have tried it with the same user logged in on the slave, and without any user logged in on the slave.
I have Test Complete and Test Execute both installed on the Slave machine. If I start them up directly, they pick up their licencing from Licence Manager located on the Master machine; so that seems to prove the network connectivity is there.
The Master is a physical machine running Windows Server 2003 (64 bit, SP2), while the Slave is a VM (VMWare) running Windows Server 2008 (32bit, SP2)
And it's TestComplete 9.10.1894.7 and TestExecute 9.10.1894.11 that are installed.
Has anybody experienced this before? or have any suggestions?
Last edited by markbeecham; 01-02-2013 at 11:59 PM.
Reason: clarify where else this is logged
TestComplete, because of how it runs tests, requires the ability to interact with the desktop. If the virtual machine is running "minimized", it may not have a "desktop" to interact with and, while you may be able to use authentication to run the test "as" a particular user, that does not necessarily guarentee that the desktop is open and able to be interacted with.
That's my best guess based upon experience... hope it helps.