|
Boost : |
Subject: Re: [boost] Breaking existing libraries
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-11-22 12:25:37
----- Original Message -----
From: "Johan Nilsson" <r.johan.nilsson_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, November 21, 2008 1:02 PM
Subject: Re: [boost] Breaking existing libraries
> Just an idea that popped out of my head - what about running (or at least
> compiling) the unit/regression tests from the _previous_ major release
> against the current release as a way to automatically detect and flag
> interface/behavioral changes?
>
> Sure, there are many potential problems with such an approach:
>
> - Some library tests are likely to also excercise code at the
> implementation/detail level.
> - Already limited testing resources (on the other hand, interface changes
> are likely to be detected by running such tests for a single, reasonably
> compliant, compiler).
> - ...
In order to have the better the author can preserve the test of the older releases and run them on the current release.
Vicente
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk