From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-23 11:01:10
From: "Beman Dawes" <bdawes_at_[hidden]>
> >2. A view which sorts tests by some measure of the failure rate, so
> >can see something about which tests are failing.
> You mean like compute the percent of tests failing for a library, and
> sort on that?
Something like that. Getting the right criteria will probably take some
> >3. A view which shows only the changes since some earlier snapshot of
> >test XML, so we can easily make sure we're not breaking something new
> >we've fixed the parts we intended to.
> Yes, that is definitively on my wish list. The XML is persistent, so it
> easy to keep track of past state. The trick is to only keep track as of
> certain points in time, like maybe "last release", "last week",
> "yesterday", "prior". I'm still trying to work that out.
Cool, you da man.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk