Re: [boost] regression test feature requests

From: David Abrahams (abrahams_at_[hidden])
Date: 2001-01-20 20:19:39

The thing I don't like about this idea is that we just got to a place where
practically the entire thing runs from C++. With your suggestion, we are
back to shell scripts, which are highly non-portable across platforms. If we
do that we may as well go back to using Python, which doesn't have that
problem ;-)
-Dave
----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>
To: <boost_at_[hidden]>; <boost_at_[hidden]>
Sent: Saturday, January 20, 2001 6:46 PM
Subject: Re: [boost] regression test feature requests

> At 06:14 PM 1/20/2001 -0500, David Abrahams wrote:
>
>  >1. There's really too much output to get a quick, clear view of what
> might
>  >have been broken. What I really want is to have the testing system
> compare
>  >the results I'm getting with the previously-checked-in state and tell me
>  >how many tests I've broken (and what I've fixed!)
>
> How about this?
>
> Don't change regression.cpp itself.
>
> Write a shell script:
>
> *  diff the old and new html files.  That will pinpoint the changes.
> *  Jiggle the diff output file a bit, so that
> *  running patch with the jiggled file results in a new html file with the
> blink attribute (or whatever) on for any changed pass/fail results.
> *  look at it with a browser.
>
> You can't beat that - blinking notice of changes right before your eyes:-)
>
> Maybe some Unix script guru can figure out how to do the "Jiggle" part
> without writing any C++ code.
>
> Smile,
>
> --Beman
>
>
>
>