Boost logo

Boost :

From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-01-19 17:31:26


At 02:40 PM 1/18/2003, Ronald Garcia wrote:
>
>
>On Fri, 17 Jan 2003, David Abrahams wrote:
>
>> Ronald Garcia <garcia_at_[hidden]> writes:
>>
>> > Is there a way to get this to work without previously running the
>entire
>> > boost test suite? I just want to test one library.
>>
>> For testing one library, forget about report generation.
>>
>> Just go to status/ and
>> [...]
>
>Thanks. Thanks to the joys of unix filtering technology, I can get this
>output to at least give me the basic information that I would like. Now
I
>am wondering, with the current set of tools, is it possible to generate
>the reports that Beman has been generating for windows for just one
>library?

Yes, I do it all the time when testing the filesystem library, and others
do it for other libs. Here is how it works:

* Rather than specifying the tests in boost-root/status/Jamfile, place a
subinclude there. For example, the current file has these:

# Tests from Jamfiles in individual library test subdirectories
subinclude libs/filesystem/test ;
subinclude libs/type_traits/test ; # test-suite type_traits
subinclude libs/regex/test ; # test-suite regex
subinclude libs/regex/example ; # test-suite regex-examples
subinclude libs/static_assert ; # test-suite static_assert

* In your own lib, usually in the "test" subdirectory, place a Jamfile with
the tests for that library. See any of the above for examples.

* To test (and report) just your library, run bjam and the reporting
programs from boost-root/libs/my-lib/test (or wherever the Jamfile lives.)

> I have found them to be very very helpful with working on
>multi_array, especially being able to track down compiler messages via
>hypertext.
>
>If this can't be done by library right now, is there any sense of the
>amount of work needed to get there?

You should be able to get it running in a few minutes. See portions of the
script in CVS: boost-root/tools/regression/run_tests.sh.

HTH,

--Beman


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk