[qmtest] Adding support for multiple programs per test

[Scott Lowrey]

Abhijeet Bisain wrote:

> I am thinking of tests where I need to spawn two processes (a client 
> and a server, for example) on two different machines. So I need a way 
> to spawn both and not have to wait for one to finish and then start 
> the other.
>
I use resources or special prerequisite tests to get the server 
configured and running.  Then, the client tests start running.  If the 
client tests can be run sequentially, things are simple.  Just create a 
test suite with all tests dependent on the resource or prereq that 
handles server startup.  QMTest will schedule the tests and ensure 
proper running order.  (Randomization is an option, too.)

If you want to run many tests concurrently against the server, there are 
many alternatives.  You can  run distributed instances of QMTest using 
the "target" metaphor (something I have not tried yet).  You can write 
run tests in parallel with QMTest's concurrency model.  Or you can "go 
it alone" and write a new test class that spawns subprocesses and 
connects to remote machines to control the clients.  This is how I 
currently deal with multiple machines and clients.

Each method has advantages and disadvantages.

- Scott