Parallel Execution of different projects on different computer.

To clarify (as I use distributed testing and love it) "WaitForCompletion" will have the runtime "wait" on that line until the respective job is finished executing. Then continue on with the logic flow. So in th below example TestComplete or TestExecute will wait on the ".Run(true)" line until the remote VM finishes executing the Job.

If it was false, the runtime would quickly start the Job and move on to the next step in the logic flow. It would NOT wait for the Job to be finished.

function Test()
{
  for (var i = 0; i < NetworkSuite.Jobs.Count - 1; i++)
    NetworkSuite.Jobs(i).Run(true);
}

Yes, because you need to be able to run the application on multiple machines.

Hi CBleunven

I will explain how I have the master and slaves run the same jobs at the same time so the master's time is not wasted (so to speak).

This is how I do it. I'm sure there are other ways to set this up.

Basically the Master function below called by TC/TE starts the entire distributed testing process. Of course this is probably best run on a remote VM through TestExecute as, with the master doing work, you couldn't do much on your local PC (unless perhaps it was not using the UI).

If this is too simplistic let me know what you would like to see and I'll try to whip something up.

// TestComplete/TestExecutetest item calls Master function
// below which starts distributed testing
function Master()
{ 
  // run slaves which do some setup and call "AllWorkerLoop()" also. 
  //Pass "false" so master does NOT wait for slaves to complete
  // but continues on once they are started
  NetworkSuite.Jobs.ItemByName("SlaveJobs").Run(false); 
  
  // master goes into this loop which slaves are also running from
  // the line above
  AllWorkerLoop(); 
}

// When the slaves startup they simply call the AllWorkerLoop() function
function Slave()
{
   AllWorkerLoop();
}

// master and slaves call same function
function AllWorkerLoop()
{
  // do work here
}