Jobs runs one after another. Tasks within a job run in parallel. So you need a job with 2 tasks, where each task runs the corresponding batch of tests. As others said, this can be done by using 2 client project suites - one containing 5 tests for one client, and another one with 7 tests for the other client. In your master project, configure the tasks to run the corresponding project suites:
Thanks for all your inputs.
The definitions of suite, project and test/testcase was useful. I find that I already use suites and projects, but in my setup, the projects contain one test/testcase each.
In other words, I have one server that runs a suite containing the client tests projects for two clients as a list of jobs.
Creating a master suite to run the two client suites should be easy. Creating a client suite with all the projects/tests seems to be a bit less straigthforward. I add projects/tests to the project page from already defined jobs, and now we have one master running a suite that starts a master suite on a client, that in turn starts slave projects/testcases on itself (the same client).
Now, I find this to actually work - after a fashion.
If I put the host name (in hosts in TestComplete) in the host address, I get an error when I try to run the project: "The local computer cannot be used as a slave host."
If I instead use the ip-address of the local machine I can actually run the project, and the testcases (sub-projects or slave projects defined in jobs) run one by one. And I have two indicators in the top right of the screen (see attachement).
Is this the way to actually make this work? Or am I doing something that potentially could give me problems?
This could potentially give you problems. The idea of a Network suite is documented that you have multiple machines in order to distribute the testing to give a better throughput by sharing out the work. Having everything run on the same machine just doesn't make sense.
But even further than that... if project 1 wants to use the mouse to click on something and project 2 wants to use the mouse to click on something different, which one wins?
Also... I would suggest a re-architecture... Having only one test case per project... well, if your application continues to grow, that will mean you could have 30, 40, 100, 200, etc. projects... it's not a sustainable architecture.
