Re: [boost] Release Tools Analysis Part II: Developer Feedback Systems

From: David Abrahams (dave_at_[hidden])
Date: 2007-08-10 11:48:14

on Wed Aug 08 2007, Stefan Seefeld <seefeld-AT-sympatico.ca> wrote:

>> Of course we're in serious danger of getting into the tool writing business 
>> again here ....
>
> I have been suggesting to look into QMTest (http://www.codesourcery.com/qmtest, which
> I happen to maintain), to drive the regression testing. It does allow the storage
> of test results in databases, and it keeps track of how tests results evolve over
> time.
>
> In fact, one of the more important features (which, unfortunately, make it hard
> to hook it up with boost.build), is that it allows the introspection of a 'test database':
> You can look at the test database (test suites, test sub-suites, as well as individual
> tests, test results, etc.) without actually running them. This is good for robustness,
> and allows to easily generate reports, involving different dimensions (across test suites,
> across platforms, across time, etc.).
>
> Oh, and QMTest makes it easy to run tests in parallel, dispatching to a compile farm, etc.

Can you give a brief summary of what QMTest actually does and how
Boost might use it?

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com
The Astoria Seminar ==> http://www.astoriaseminar.com