Forum Discussion

shubhangi's avatar
shubhangi
Contributor
13 years ago

TestExecute takes a while to launch

Hi,

I am using NetworkSuite to execute test on multiple clients.

I am having 3 virtual machines on which test are going to be run. When I double click on TE icon, It takes a while to lauch it.

Hence while running test,  test complete fails to launch TestExecute and errors out as "Verification failed. Unable to launch remote instance of TestExecute"



I am using TC/TE 8.7. My License manager is on the same network as of master and slaves. Verification of each slaves works fine.

If launch TE manually on slaves and then start the test run, It runs perfectly fine.



Is there any setting where I can change the timeout for launching TE.

Any thoughts/tips would be greatly appreciated.



Thanks,

Shubhangi

3 Replies

  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    13 years ago
    Hello Shubhangi,

    There is not timeout setting for launching TestExecute. To work around the problem, you can launch TestExecute on your remote computers beforehand, and then run your tests with the Use previous instance option set to Use Previous TestComplete Instance. You can find more information on this option in the "Editing Task Properties" Help topic.

    Please let us know whether this helps, and whether you have any additional questions.

    By the way, could you please specify how much time exactly does it take for TestExecute to be launched on your remote computers? Does it take more than several minutes?

    Thank you.
  • shubhangi's avatar
    shubhangi
    Contributor
    13 years ago

    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

  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    13 years ago

    Hello Shubhangi,


    The problem you describe is expected if you have multiple virtual slave machines running on a single physical machine. And the more slaves you add, the lower the performance of each particular slave gets and the more time it takes for TestExecute to be launched.

    It is good that you have already found a suitable workaround for this problem.

    Good luck with your testing.