Boost logo

Boost :

From: David Abrahams (abrahams_at_[hidden])
Date: 2000-11-02 17:22:29

----- Original Message -----
From: "Beman Dawes" <beman_at_[hidden]>

> I'm starting to modify the regression test driver program to execute as
> well as compile the test programs. The status table will report two
> entries per cell:
> yes/yes == compile and test both returned 0
> yes/no == compile OK but test did not return 0
> yes/-- == compile OK but test not run; need better test program
> no/-- == compile failed, test not run; no point since compile failed
> The "no" entries are bold so they stand out.
> While this gets the ball rolling, it isn't totally effective without
> modifying the test programs to always use the return code to indicate
> success or failure.
> That in turn would be helped by macros to use instead of assert to pass
> failure return code. One macro to exit on failure, another to set global
> state to failure but continue program execution.
> I know this isn't as good as DejaGnu, but it is very easy to get started.
> Comments?

It all sounds good, but it won't fix the particular problem I'm having,
which is that the tests clearly need to be modified (perhaps a simple #ifdef
can be removed) in order to exercise more of the code under MSVC. I don't
know who is qualified to do this. John Maddock, perhaps?


Boost list run by bdawes at, gregod at, cpdaniel at, john at