[qmtest] Multiple databases

[Stefan Seefeld]

Morten Mossige wrote:

> I'm still not sure if I fully understand how to do this.
> But let me give an ex. of how I would like have it:
> I have several different applications, placed in the following
> directory structure:
> 
> root+app+---app1--+--src
>        |         |
>        |         +--test
>        |
>        +---app2--+--src
>        |         |
>        |         +--test
>        |
>        +---app3--+--src
>        |         |
>        |         +--test
>        |
>        |
>       +MasterTest
> 
> I would like to have a single test database in each app<n>\test
> directory which tests only this application. But in the MasterTest dir
> I would like to have a testdatabase which will run all the subtests +
> integration test (tests which require several app's running together.
> The tests in app<n>\test will typically be runned by developers, while
> the test in MasterTest will be runned automatically by the daily build
> system (build server).

Your description sounds like a sensible database design to me. Please
note that, while QMTest comes with a set of 'extension classes' built-in,
it is also designed for extensibility, specifically to make it possible to
easily customize it.
I believe you may be able to get best results if you write your own
Database and Test classes, following the documentation, for example

http://www.codesourcery.com/public/qmtest/qm-snapshot/share/doc/qmtest/html/tutorial/extending-database-classes.html
http://www.codesourcery.com/public/qmtest/qm-snapshot/share/doc/qmtest/html/tutorial/extending-test-classes.html

> Also: How is the best way of getting a html based report out of the
> MasterTest test?

QMTest stores testrun results in result files. The specific format of a result
file (or in fact whether to write to a file or to a results database, or...)
is as extensible as most other aspects; you may well write your own 'result_stream'.

The QMTest command line interface provides a 'report' command that will process
(potentially multiple) testrun results files into a single test report (XML).
We provide an XSLT stylesheet to translate that into other media (such as HTML),
though you likely want to customize that process as is typical for XSLT processing
of XML input.

Regards,
		Stefan

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