From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-05-06 14:04:36
Stefan Seefeld wrote:
> David Abrahams wrote:
>>> * See all tests, as part of the test database structure (i.e. their
>>> organization into test suites)
>>> * See meta data associated with tests, such as
>>> - what kind of test
>>> - expected outcome, per platform
>>> - dependencies, prerequisites, etc.
>> How would that help with robustness?
> There have been a number of cases where the regression harness picked up
> (and reported) stale results, just because old executables / results were
> lying around in the build tree. It didn't 'know' that the test actually
> had been removed from the test suite.
Boost.Build outputs the list of all tests. The only reason regression.py
does not use that information to prune test results is because
nobody implemented such pruning. Just to clarify...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk