Re: [Adonthell-devel] Unit testing in Adonthell

[Josh Glover]

On 26 March 2010 09:57, Kai Sterker <address@hidden> wrote:

> On Fri, Mar 26, 2010 at 9:24 AM, Josh Glover <address@hidden> wrote:
>
>> I recommend that developers always use the --enable-dev-build flag,
>> and run "make check" instead of just make.
>
> It's failing for me, even though I have gmock and gtest installed
> (version 1.4.0). However, there are no .pc files for the two that
> pkg-config could pick up. Instead there are scripts gmock-config and
> gtest-config that would provide the required cflags and libs.

D'oh! You need these two patches:

* 
http://groups.google.com/group/googletestframework/browse_thread/thread/49a10a713d016128
* 
http://groups.google.com/group/googlemock/browse_thread/thread/af151f3a605e1656

Sorry. This of course means that you will need to build googletest and
googlemock from source, but that shouldn't slow you guys down much. :)

> I guess it might have made things for Tyler a lot easier if all that
> code would have had unit tests. I'll try to better myself in that
> regard.

I personally practice Test-Driven Development:

http://en.wikipedia.org/wiki/Test-driven_development

I find it makes coding lots of fun; YMMV. :)

> Not sure how easy it would be, but replicating the modules
> under test/ and keeping mocks and test cases there might be a way to
> keep things at least a little bit clearer.

That was my original plan, but it was a bit of a PITA. I think that as
long as we follow the convention that the tests for class foo are in
test_foo.cc, it will at least line up all the tests in the output of
ls.

-- 
Cheers,
Josh