Re: [Boost-cmake] CMake for development testing

Subject: Re: [Boost-cmake] CMake for development testing
From: Ingmar Vanhassel (ingmar_at_[hidden])
Date: 2009-06-05 18:32:55

Excerpts from David Abrahams's message of Fri Jun 05 23:09:44 +0200 2009:
> However, the way CMake reports failures really doesn't fit in with my
> development workflow.  I'm doing 
> 
>       make Python-test
> 
> and what I get back looks something like this:
> 
>     ...
> 
>  67/ 79 Testing Python-result                    Passed
>  68/ 79 Testing Python-string_literal         ***Failed
>  69/ 79 Testing Python-borrowed               ***Failed
>  70/ 79 Testing Python-object_manager            Passed
>  71/ 79 Testing Python-copy_ctor_mutates_rhs     Passed
>  72/ 79 Testing Python-upcast                    Passed
>     ...
> 
> What's the nature of these failures?  It doesn't tell me.  
> 
> I found the output of those tests is squirreled away in
> libs/python/Testing/Temporary/LastTest.log below my build directory.
> How?  rgrep.  This stuff should be made mroe obvious.

make Python-test ARGS=--verbose, to pass arguments to ctest.

That'll give you verbose output for all the tests though, not just those
that failed. I'm not sure how you'd conveniently accomplish the latter.

> Worse, it's in there among all the successful test output, so I have to
> dig around to find the failures.  Yes, there's another file called
> LastTestsFailed.log that tells me which tests failed.  So the full
> procedure for addressing failures is to find the LastTestsFailed.log
> file, then look for each test name listed there in the LastTest.log file
> and find the diagnostic output.  There /has/ to be a better way.  Maybe
> there is, and I just haven't learned about it yet?