|
Boost : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-11-19 15:59:00
At 12:17 PM 11/19/2003, David Abrahams wrote:
>Darren Cook <darren_at_[hidden]> writes:
>
>> I want to set up a test suite for one of my own libraries, and started
>> looking at how Boost does this. In status/Jamfile it has lines like:
>> [ run libs/array/array1.cpp ]
>>
>> I had a look in array1.cpp and all it does is output to stdout. I
>> don't see any asserts, and I cannot find a file of expected output to
>> compare to. Is just running to completion enough to pass the test, or
>> am I missing something?
>
>Nope, you're not missing anything. It might be possible to add
>expected results comparison, but that's not currently part of the
>system.
Note that because the current test framework simply decides if a test
passes or fails based on the return code, it can be used to call any
program which uses that convention.
So you could have a test that called an expected results comparison testing
program, as long as that program reported pass/fail results via its return
code.
One of the uses of that I've often thought of was to run execution timings.
--Beman
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk