Forum Discussion
Hi Julia,
Thanks for your reply. I am using same suggestion at the
moment. I use following code to launch and terminate TestExecute , before
starting test run
function StartEndTestExecute(hostsList)
{
Log.Message("Start StartEndTestExecute");
var
vmHost = dotNET.Vestris_VMWareLib.VMWareVirtualHost.zctor();
vmHost.ConnectToVMWareWorkstation();
for(
i=0; i<hostsList.length; i++)
{
var
hostname = hostsList.SelectSingleNode("Name").text;
var
vmxFile = hostsList.SelectSingleNode("VMXLocation").text;
var
vmxFileWithDblSlash=aqString.Replace(vmxFile, "\\",
"\\\\");
vmMachine = vmHost.Open(vmxFile);
vmMachine.LoginInGuest("DPAdmin","Password");
vmMachine.RunProgramInGuest_2("C:\\Program Files (x86)\\Automated
QA\\TestExecute 8\\Bin\\TestExecute.exe","/exit");
Log.Message("End
StartEndTestExecute");
}
TestExecute takes more than half a minute on WinXp and bit
more on Win7. But this is enough to make test run fail, where testcomplete
tries to launch TE instance on remote instance.
Just for your information, We have 17 floating TE licenses stored
on a license manager. Earlier we were using only 7-8 TE licenses. This issue appeared
when we started adding more slaves (but less than 17).
Regards,
Shubhangi
Related Content
- 8 years agovatbub
- 5 years agodjvakarjoshi1
Recent Discussions
- 2 hours agoSubhraDas
- 8 hours agoJacobjacob44