Hi Bo,
We put together a Wiki page comparing Boost Testing and Google Test in
ITK. It has examples of how to write (ITK) tests in both frameworks and
CTest integration.
http://www.itk.org/Wiki/Proposals:Increasing_ITK_Code_Coverage
-dan
On 7/9/10 6:37 AM, "Bo Thorsen" wrote:
> Hi people,
On 7/12/2010 2:00 PM, Torri, Stephen CIV NSWCDD, W15 wrote:
From: cmake-boun...@cmake.org on behalf of Ryan Pavlik
Sent: Mon 7/12/2010 9:59 AM
To: cmake@cmake.org
Subject: Re: [CMake] CTest examples
I'm been using Boost Test, and I've written a module that lets you add the
executab
> From: cmake-boun...@cmake.org on behalf of Ryan Pavlik
> Sent: Mon 7/12/2010 9:59 AM
> To: cmake@cmake.org
> Subject: Re: [CMake] CTest examples
>
> I'm been using Boost Test, and I've written a module that lets you add the
> executable and the tests (where
>
.
Thanks
Date: Fri, 9 Jul 2010 14:54:46 -0700
From: chillery-cm...@lambda.nu
To: b...@askmonty.org
CC: cmake@cmake.org
Subject: Re: [CMake] CTest examples
For CTest, running a test means running an executable and seeing
whether the result of that pr
Den 09-07-2010 19:03, Eric Noulard skrev:
2010/7/9 Bo Thorsen:
Hi people,
I have converted a set of applications to cmake and cpack, and now have my
eyes set on ctest.
I'd like to hear if someone here has some good advice, or links to good
advice, on how to structure tests. I'm searching for h
Den 10-07-2010 00:05, David Cole skrev:
On Fri, Jul 9, 2010 at 5:54 PM, Chris Hillery mailto:chillery-cm...@lambda.nu>> wrote:
[...]
On Fri, Jul 9, 2010 at 4:37 AM, Bo Thorsen mailto:b...@askmonty.org>> wrote:
[...]
To sum it up, I'm looking for real life advice on what you g
:46 -0700
From: chillery-cm...@lambda.nu
To: b...@askmonty.org
CC: cmake@cmake.org
Subject: Re: [CMake] CTest examples
For CTest, running a test means running an executable and seeing whether the
result of that process is 0 (success) or not 0 (failure). It is also possible
to scan the output of
On Fri, Jul 9, 2010 at 5:54 PM, Chris Hillery wrote:
> For CTest, running a test means running an executable and seeing whether
> the result of that process is 0 (success) or not 0 (failure). It is also
> possible to scan the output of the executable for certain regular
> expressions to determine
For CTest, running a test means running an executable and seeing whether the
result of that process is 0 (success) or not 0 (failure). It is also
possible to scan the output of the executable for certain regular
expressions to determine success or failure.
It's a very simple and somewhat limited m
2010/7/9 Bo Thorsen :
> Hi people,
>
> I have converted a set of applications to cmake and cpack, and now have my
> eyes set on ctest.
>
> I'd like to hear if someone here has some good advice, or links to good
> advice, on how to structure tests. I'm searching for help on how to put
> different te
Hi people,
I have converted a set of applications to cmake and cpack, and now have
my eyes set on ctest.
I'd like to hear if someone here has some good advice, or links to good
advice, on how to structure tests. I'm searching for help on how to put
different tests into what executables. On h
11 matches
Mail list logo
