John Maddock 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. I sincerely believe that, no matter whether QMTest will be seriously considered in this context, the concepts it builds on, definitely should. Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...