[qmtest] instantiating suites

[Mark Mitchell]

On Tue, 2004-01-13 at 06:56, Stefan Seefeld wrote:
> hi there,
> 
> I just realized that some code of mine implementing a test database
> doesn't work any more with a fresh update as the 'Suite' class has
> changed (i.e. has become an extension).
> 
> What is the suggested way to instantiate a suite as was possible
> up to the end of last year, i.e. via
> 
> Suite(self, id, implicit = 1, test_ids = tests, suite_ids = suites)
> 
> ? I notice an 'explicit suite' class now available as an extension,
> i.e. in the 'classes' directory. How can I access / instantiate that
> directly ?

Use:

 from explicit_suite import ExplicitSuite

> Is there any documentation available explaining why the extension
> mechanism works the way it does (and, in fact, what extensions are
> designed for, which classes should be extensions etc.; I'm a bit
> astonished to see Suite becoming an extension...)

We've wanted for a while to make it so that databases only store
extensions; that's a much more uniform model, and will permit some new
database features in future.

You've got all the documentation that exists at this point. :-(

The basic idea of extensions are that anything that test developers
(i.e., the people who take QMTest and create testsuites for end-users to
run) develop should be a subclass of Extension.

-- 
Mark Mitchell <mark at codesourcery.com>
CodeSourcery, LLC