Boost logo

Boost Testing :

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2007-12-02 05:10:05

David Abrahams schrieb:
> on Fri Nov 30 2007, David Abrahams <> wrote:
>> In particular, the tests that use output_test_stream supply filenames
>> that are interpreted relative to the current working directory.
>> That's not the best possible practice, for reasons of "hygiene:" if
>> testing Boost causes the Boost tree to be modified, it's hard to be
>> sure that one is testing the same thing the next time around.
>> Furthermore, it means one can't test from within a read-only copy of
>> the Boost sources. This bit me as I tested from an NFS-mounted
>> working copy.
> Oh, and I realize this is going to be a problem as soon as my testing
> machines or processes are sharing a working copy, because they will
> collide when trying to write these files out.

Boost.Filesystem and Boost.Serialization also create temporary files in
the current working directory, IIRC.


Boost-testing list run by mbergal at