November 2013 - Boost-users - lists.preview.boost.org

Question for Boost.Threads and Boost.Test
by young 20 Jan '14

20 Jan '14

According to Boost document, Boost.Test can only be statically linked. Boost.Threads can only be dynamically linked. Then what boost_unit_test_framework-vc100-mt-1_53.lib for? Is it for dynamically linked dll? what libboost_thread-vc100-mt-1_53.lib for? Is it for static library? -- View this message in context: http://boost.2283326.n4.nabble.com/Question-for-Boost-Threads-and-Boost-Tes… Sent from the Boost - Users mailing list archive at Nabble.com.

4 6

[Test] Where to learn about boost::itest::mock_object?
by Mateusz Loskot 20 Jan '14

20 Jan '14

Hi, I'm looking for a simple mocking library to use together with Boost.Test. There is Turtle (aka Boost.Mock) and googlemock. During retrospection of the big thread on Boost.Test future [1], I found this curious post by Gennadiy [2] about mock_object. I had no idea such facility lives in Boost.Test and it looks it's been there for very long time. I can't find any documentation about mock_oboject, only a couple of examples. So, I have a few questions: Is the mock_object an internal feature or is it dedicated (and ready) to use by Boost.Test users? What are basic features of this mocking facility? How does it compare to Turtle or googlemock? [1] http://thread.gmane.org/gmane.comp.lib.boost.devel/234297 [2] http://thread.gmane.org/gmane.comp.lib.boost.devel/234297/focus=234621 [3] find /home/mloskot/dev/boost/_svn/trunk/libs/test -type f | xargs grep mock_object Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

4 4

Does Boost.Test cover 'golden file approach'?
by Journeyer J. Joh 13 Jan '14

13 Jan '14

Hello, I know almost nothing about 'golden file approach'. http://weblogs.java.net/blog/alexeyp/archive/2007/02/testing_command.html >From this blog, you can find the term 'golden file approach'. I want to know if Boost.Test cover this kind of testing. Can I implement 'golden file approach' with Boost.Test? If so please provide me more information about it. Thank you very much. ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m ----------------------------------------

3 5

[Test] using output_test_stream to compare in the middle of a file
by Lloyd 13 Jan '14

13 Jan '14

Hi, We need to test a function which reads a "record" from a binary file. We want to compare the buffer with the "record" in input file.We know the offset of the record in input file. How can we compare the output_test_stream with a certain offset (and length) of the file? or is there any alternative for this? Thanks, Lloyd

2 1

Boost.Test segfault clang++3.3 macports cmake
by Dave Gomboc 13 Jan '14

13 Jan '14

I am getting a segmentation fault when attempting to use Boost.Test. I suspect that I don't have something set up correctly -- your assistance in remedying this would be appreciated. I am using clang++-mp-3.3 as installed by MacPorts on OS X 10.8.4. Here's the crash, which occurs after Boost.Test reports "*** No errors detected". Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 0x000000010006f6d6 in boost::unit_test::test_unit::~test_unit () (gdb) bt #0 0x000000010006f6d6 in boost::unit_test::test_unit::~test_unit () #1 0x000000010003bb5f in boost::unit_test::master_test_suite_t::~master_test_suite_t () #2 0x000000010003bcdd in boost::unit_test::framework_impl::~framework_impl () #3 0x00007fff8f465307 in __cxa_finalize () #4 0x00007fff8f466f57 in exit () #5 0x00007fff96ddc7e8 in start () (gdb) Here's a somewhat simplified version of what I have: ==== UseBoostUnitTestFramework.hpp ==== #pragma clang diagnostic push #pragma clang diagnostic ignored "-Wall" #pragma clang diagnostic ignored "-Wdisabled-macro-expansion" #pragma clang diagnostic ignored "-Wexit-time-destructors" #pragma clang diagnostic ignored "-Wextra-semi" #pragma clang diagnostic ignored "-Wglobal-constructors" #pragma clang diagnostic ignored "-Wmissing-prototypes" #pragma clang diagnostic ignored "-Wsign-conversion" #pragma clang diagnostic ignored "-Wundef" #pragma clang diagnostic ignored "-Wweak-vtables" #include <boost/test/unit_test.hpp> #pragma clang diagnostic pop ==== HaveBoostUnitTestFrameworkDefineMain.cpp ==== #define BOOST_TEST_MODULE All_Tests #include "UseBoostUnitTestFramework.hpp" /* commenting out the next 3 lines makes no difference */ namespace boost { namespace unit_test { namespace framework { master_test_suite_t & master_test_suite(); } } } // namespace boost::unit_test::framework ==== CMakeLists.txt ==== cmake_minimum_required(VERSION 2.8.10 FATAL_ERROR) cmake_policy(VERSION 2.8.10) project (Foo) add_definitions(-DBOOST_TEST_DYN_LINK) add_library (foo SHARED Foo1.hpp more files... UseBoostUnitTestFramework.hpp Foo1.cpp more files... ) find_package(Boost COMPONENTS unit_test_framework REQUIRED) include_directories(${Boost_INCLUDE_DIRS}) file(GLOB_RECURSE test_source_files *.unit_tests.cpp) link_directories(${Boost_LIBRARY_DIRS}) add_executable(all_tests HaveBoostUnitTestFrameworkDefineMain.cpp ${test_source_files}) target_link_libraries(all_tests foo ${Boost_UNIT_TEST_FRAMEWORK_LIBRARY} ) set(CTEST_OUTPUT_ON_FAILURE TRUE) enable_testing() add_test(all_tests all_tests) set(CMAKE_C_COMPILER "clang-mp-3.3") set(CMAKE_C_FLAGS "-Weverything --std=c11 -O3 -DNDEBUG") set(CMAKE_CXX_COMPILER "clang++-mp-3.3") set(CMAKE_CXX_FLAGS "-ferror-limit=1 --std=c++1y -stdlib=libc++ -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -Wno-padded -O3 -DNDEBUG") ==== Foo1.hpp ==== (has declarations, but nothing that depends on Boost at all -- nor does any other non-test file) ==== Foo1.cpp ==== (has definitions, but nothing that depends on Boost at all -- nor does any other non-test file) ====Foo1.unit_tests.cpp ==== #include "Foo1.hpp" #include <string> #pragma clang diagnostic push #pragma clang diagnostic ignored "-Wglobal-constructors" #include "UseBoostUnitTestFramework.hpp" BOOST_AUTO_TEST_SUITE(Bar1) BOOST_AUTO_TEST_CASE(foobar1) { BOOST_CHECK_EQUAL(std:string("a"), std::string("a")); } BOOST_AUTO_TEST_CASE(foobar2) { BOOST_CHECK_EQUAL(true, true); } BOOST_AUTO_TEST_SUITE_END() BOOST_AUTO_TEST_SUITE(Bar2) BOOST_AUTO_TEST_CASE(barfoo1) { BOOST_CHECK_EQUAL(1, 1); } BOOST_AUTO_TEST_CASE(barfoo2) { BOOST_CHECK_EQUAL(0, 0); } BOOST_AUTO_TEST_SUITE_END() #pragma clang diagnostic pop

3 2

[test] floating point comparison
by Matthijs Möhlmann 13 Jan '14

13 Jan '14

Hello all, I've the following test program: #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MAIN #define BOOST_TEST_MODULE Master test suite #include <boost/test/unit_test.hpp> BOOST_AUTO_TEST_CASE(TestCase) { BOOST_REQUIRE_CLOSE_FRACTION(45.00f, 45.17f, 0.004f); } When I compile it with the following line: g++ -o main.o -c -Werror -Wall -std=c++11 -fvisibility=hidden -fvisibility-inlines-hidden -DBOOST_SPIRIT_USE_PHOENIX_V3 -DUTEST -g main.cpp g++ -o main main.o -lboost_unit_test_framework I get the following output: Running 1 test case... *** No errors detected If I lower the tolerance to 0.0004f then I'll get the following: Running 1 test case... main.cpp(8): fatal error in "TestCase": difference{0.00376352} between 45.00f{45} and 45.17f{45.1699982} exceeds 0.00039999999 *** 1 failure detected in test suite "Master test suite" Why does it say that the difference is 0.00376352 and not 0.17....... ? Regards, Matthijs Möhlmann

4 4

BOOST.TEST Mixing automatic and manual test registratioI
by Manuel Maier 13 Jan '14

13 Jan '14

Hi, Is it possible to mix manual and automatic test registration in Boost,.Test. Example: BOOST_AUTO_TEST_SUITE( ExampleTestSuite ) BOOST_AUTO_TEST_CASE( testcase1 ) { BOOST_TEST_MESSAGE("Test 1 in Example Test Suite"); BOOST_WARN_EQUAL(1, 1); BOOST_REQUIRE_MESSAGE(5 > 1, "Here is an example message. Something may be wrong"); } BOOST_AUTO_TEST_SUITE_END() Now I want to manually add a testcase to this testsuite. This seems to be important for me, as there is no automatic registration version for BOOST_PARAM_TEST_CASE(...) I also made a manualTestRegstration: test_suite* TestSuiteA = BOOST_TEST_SUITE("test_suiteA"); void manualTestCaseRegistration() { TestSuiteA->add( &test_case ); framework::master_test_suite().add( TestSuiteA ); } Is it possible to add a manual testcase(e.g.: test_case_b) to the ExampleTestSuite? Searching the internet I stumbled over following thread: https://svn.boost.org/trac/boost/ticket/7000 But it seems to me this patch never made it to release(at least until now). In fact( I guess) this could/would be exactly the feature I am looking for. Kind Regards and thanks for help Manuel _____________________________________________ Manuel Maier, B. Eng. Business Unit "Motion" / Research & Development Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. B&R Strasse 1 5142 Eggelsberg Austria Tel: +43 7748 6586 Fax: +43 7748 6586 - 24 Email: manuel.maier(a)br-automation.com http://www.br-automation.com ____________________________________________________________ Firmenbuchnummer: Landesgericht Ried im Innkreis / FN 111651 v

3 3

[boost.test] How to register custom exception for auto test?
by Jörg Becker 13 Jan '14

13 Jan '14

Hi, I'm using the test library of boost 1.49.0 for my unit tests. It works fine so fare, but if my program throws an error, I get the default error message unknown location(0): fatal error in "excption1_test": unknown type, witch hides the original error message. I tried to register an error translator, but without success. Here is what I tried (modified test/test/custom_exception_test.cpp to use auto test with global fixture): #define BOOST_TEST_MODULE "boost test custom_exception_test" #include <boost/test/unit_test.hpp> #include <boost/test/unit_test_monitor.hpp> using namespace boost::unit_test; BOOST_AUTO_TEST_SUITE( custom_exception_testsuite ) struct my_exception1 { explicit my_exception1( int res_code ) : m_res_code( res_code ) {} int m_res_code; }; void throw_my_exception1() { throw my_exception1( 12 ); } void my_exception1_translator( my_exception1 ) { BOOST_TEST_MESSAGE( "Caught my_exception1" ); } class my_config { public: my_config () { unit_test_monitor.register_exception_translator<my_exception1>( &my_exception1_translator ); } }; BOOST_GLOBAL_FIXTURE( my_config ) BOOST_AUTO_TEST_CASE( excption1_test ) { throw_my_exception1(); } BOOST_AUTO_TEST_SUITE_END() Can anybody tell me what I'm missing? Thanks, Jörg

3 5

[BOOST]BOOST_AUTO_TEST_CASE_TEMPLATE vs BOOST_AUTO_TEST_CASE
by Hemanth Choudary M V (RBEI/ETA1) 13 Jan '14

13 Jan '14

Hi, Scenario1: Both files are present in the same Project BoostUnitTest. fileA: typedef boost::mpl::list<long long,unsigned char> test_types; BOOST_AUTO_TEST_SUITE(MySuite) BOOST_AUTO_TEST_CASE_TEMPLATE( my_test, T, test_types ) { BOOST_CHECK_EQUAL( sizeof(T), (unsigned)4 ); } BOOST_AUTO_TEST_SUITE_END() fileB: typedef boost::mpl::list<long long,unsigned char> test_types; BOOST_AUTO_TEST_SUITE(MySuite) BOOST_AUTO_TEST_CASE_TEMPLATE( my_test, T, test_types ) { BOOST_CHECK_EQUAL( sizeof(T), (unsigned)4 ); } BOOST_AUTO_TEST_SUITE_END() As shown above, MySuite is extended across 2 files fileA and fileB. The BOOST_AUTO_TEST_CASE_TEMPLATE name is same across the both the files and and the suite name is also same across both the files.. Boost is able to differentiate between the 2 test cases and the test cases are executed. Scenario2: fileA: BOOST_AUTO_TEST_SUITE(MySuite) BOOST_AUTO_TEST_CASE( my_test) { BOOST_CHECK_EQUAL(1,1); } BOOST_AUTO_TEST_SUITE_END() fileB: BOOST_AUTO_TEST_SUITE(MySuite) BOOST_AUTO_TEST_CASE_TEMPLATE( my_test ) { BOOST_CHECK_EQUAL( 1,1 ); } BOOST_AUTO_TEST_SUITE_END() In the scenario2, I get a compile time error (Error 1 error LNK2005: "public: void __thiscall mySuite::insuite2::test_method(void)" (?test_method@insuite2@mySuite@@QAEXXZ) already defined in BoostUnitTest.obj) which basically suggests that one or more multiply defined symbols are found. Why is the behaviour different in these 2 scenarios? How is Boost able to differenciate between the 2 test cases in Scenario1? Mit freundlichen Grüßen / Best Regards, Hemanth Choudary MV RBEI/ETA1

3 2

--run_test and using this to run a subset of Testcases.
by Manuel Maier 13 Jan '14

13 Jan '14

Hi I am looking for help considering running sets of Testcases/Testsuites. First off, is there a possibility to do a negative selection. i.e. tell boost.test to NOT run certain Testcases/testsuites? Further is it possible to run sets of Testcases(which may reside in different testsuites)? Assume following test tree: MASTER suite1 case1 case2 suite2 testcase1 testcase2 suite3 subsuite testcase1 Now lets say I wanna run testcase case1, testcase2 and the subsuite testsuite. Is this even possible? Kind Regards and thanks a lot for help Manuel Maier _____________________________________________ Manuel Maier, B. Eng. Business Unit "Motion" / Research & Development Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. B&R Strasse 1 5142 Eggelsberg Austria Tel: +43 7748 6586 Fax: +43 7748 6586 - 24 Email: manuel.maier(a)br-automation.com http://www.br-automation.com ____________________________________________________________ Firmenbuchnummer: Landesgericht Ried im Innkreis / FN 111651 v

5 6