Comments on: C++ Unit Testing With Boost.Test

By: emc testing lab

emc testing lab — Sat, 28 Jan 2012 02:42:42 +0000

emc testing lab…

[...]a little madness » Blog Archive » C++ Unit Testing With Boost.Test[...]…

By: KEPS

KEPS — Sun, 09 Oct 2011 09:04:11 +0000

Thank goodness for some clarity on this! Thanks very much for your nice tutorial.

By: Marco Di Bartolomeo

Marco Di Bartolomeo — Mon, 01 Aug 2011 17:22:23 +0000

A very nice Boost.Test tutorial! Thank you.

By: Very nice and concise blog post about Boost.Test | The Lone C++ Coder's Blog

Fri, 18 Mar 2011 22:22:20 +0000

[...] a little madness » Blog Archive » C++ Unit Testing With Boost.Test This entry was posted in C++ and tagged c++, unit testing. Bookmark the permalink. ← Emacs 23.3 released [...]

By: Robert

Robert — Thu, 27 May 2010 07:38:38 +0000

Is there a way to put separate test suites in different files such that I can either compile and run them individually or all together? Sometimes I only want to run the tests for a single module I’m working on, other times I want to run all the tests for the entire project.

By: Gui

Gui — Wed, 17 Mar 2010 10:27:50 +0000

Thanks Jason, I tried to cross compile Boost.Test through bjam. It is pretty easy to use and automatize. Using Bjam with the “–with-test” parameter will only compile Boost.Test.

By: Jason

Jason — Sun, 14 Mar 2010 08:17:21 +0000

Hi Gui,

AFAIK Boost.Test does not require any of the other Boost libraries. I haven’t tried installing just Boost.Test to verify this, though.

By: Gui

Gui — Wed, 10 Mar 2010 09:45:50 +0000

Does anyone know if it is possible to use boost.test without any other boost library ?

By: Gui

Gui — Tue, 09 Mar 2010 14:20:50 +0000

Did not see the previous answer. Seems that on ubuntu boost is multi-threading enable. Following line solve the problem :
g++ -ohello -lboost_unit_test_framework-mt hello.cpp

By: Ulrik Gammelby

Ulrik Gammelby — Tue, 09 Mar 2010 14:11:03 +0000

I agree with the other posters, thanks for this gentle and useful introduction to boost tests. The official documentation is WAY too heavy on (irrelevant) words, such as general chatter about why testing is a good thing and long elaborations on how things looked earlier in the framework, confusing the picture if you are just scanning for a specific piece of information.