|
|
Boost Testing : |
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-09-15 21:43:26
Beman Dawes wrote:
> Rene Rivera wrote:
>> Beman Dawes wrote:
>>
>>> What can be done to ensure the problem does not reoccur?
>> Hm, hard question to tackle, since managing multiple disparate processes
>> is never easy.
>>
>>> What can be done to automatically detect and report the problem if it
>>> does reoccur?
>> The one idea that needs investigation, that Robert has mentioned a few
>> times, is in doing regression testing for the testing system itself, and
>> related tools. We have tests for some of the tools involved, mainly
>> bjam, Booost.Build, and some others, but the coverage and depth is
>> spotty. The one idea I've had is to create a mini-Boost branch that can
>> track the current state but runs a minimal set of tests. I.e. black-box
>> testing the testing system as a whole.
>
> Hum... One simple change would at least have made the problem obvious a
> lot sooner;
The problem is that *any* change to the report generation is not simple.
> What program would have to be changed to display the revision number?
> Maybe I'll give this a try.
Eek, if you are that brave, it's someplace in the XSL files in
tools/regression/xsl_reports/xsl. And I really have no idea where, let
alone how.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo