[qmtest] qmtest targets: I'm missing something...

[Stefan Seefeld]

J.T. Conklin wrote:

> But unit tests are run on the master box, which isn't scaling with the
> number of developers and the number of tests.  So what I'd like to do
> is set up a pool of "test" nodes, where qmtest dispatches the tests.
> But what I really want to do is to set up several pools.  Development
> Engineering has their pool that is shared among all, but Release
> Engineering has an dedicated pool so they have more predicable behavior.
> 
> My question was if I add the set of all development and release test
> nodes as targets to the QMTest/targets file, perhaps like:
> 
>         $ qmtest create-target riptide rsh_target.RSHTarget
>         $ qmtest create-target ebbtide.rsh_target.RSHTarget
>         $ qmtest create-target hogtied.rsh_target.RSHTarget
> 
> How do I select what subset of these are actually used?  Or is the
> something obvious I'm missing that a target database represents a
> pool, and to do what I want is a simple matter of creating two of
> the target databases?

Yes, I think what you want is multiple target files, each describing
the set of nodes that are part of the different pools.
Then, one team runs 'qmtest -t devel', and the other 'qmtest -t release',
or somesuch.

> Since target_group filtering has been mentioned, how does that work?
> I'm not seeing anything that mentions what (attribute?) needs to be
> set for the Test class/instance for this to occur.

The tutorial describes (briefly) the concept of a 'target group':

http://www.codesourcery.com/public/qmtest/qm-snapshot/share/doc/qmtest/html/tutorial/concepts-targets.html

Also, the API docs may be of some help (here the Test base class):

http://www.codesourcery.com/public/qmtest/qm-snapshot/share/doc/qmtest/html/manual/public/qm.test.test.Test-class.html

As Mark mentions, if you set a test's 'target_group' parameter to
something other than '*', it will be used to match targets against
(from the currently selected target file), so the test gets dispatched
to an appropriate target (or skipped if there is no match).

Regards,
		Stefan

-- 
Stefan Seefeld
CodeSourcery
stefan at codesourcery.com
(650) 331-3385 x718