CppUnit Code coverage Tool

fdbcv jyhtgh — Sat, 22 May 2021 06:06:57 -0000

I wanna use it for my new project here but the main issue for me is how to run this software on my project please help me by sharing its complete process you can see my blog here for further details.

Unable to link CPPunit test

Alexander Lindsay — Fri, 13 Sep 2019 18:06:54 -0000

Experiencing the exact same issue when linking to libMesh unit tests on Ubuntu 16.04 with manually built cppunit (e.g. configure; make; make install

Unable to link CPPunit test

Dave Clark — Mon, 22 Jul 2019 16:07:07 -0000

Hello;

I'm getting an error when attempting to link a CPPunit test (using Netbeans on RHEL). Another developer is able to link the test successfully, and we both have the same cppunit and cppunit-devel packages installed, so I'm not sure what's going on here. The error is:

build/Debug/GNU-Linux/tests/tests/abcTest.o:(.rodata._ZTIN7CppUnit17AdditionalMessageE[_ZTIN7CppUnit17AdditionalMessageE]+0x10): undefined reference to `typeinfo for CppUnit::Message'

Any ideas? Thanks in advance.

Problem with registration of testsuite

cmaynard — Fri, 14 Jun 2019 17:24:50 -0000

I had this same issue. This was a good explanation and it looks like the code has been updated to include Portability.h. Unfortantely that wasn't the problem. Turned out to be something completely different. This macro, CPPUNIT_TEST_SUITE_REGISTRATION, is used in my source file but the issue was in the header file. There was a missing semi-colon at the end of my class declaration. The missing semi-colon wasn't even reported as a compilation error, only the errors with the macro. To discover the problem, I took my test down to a skeleton program and commented out the call to CPPUNIT_TEST_SUITE_REGISTRATION in the source file. This is when the compiler reported the missing semi-colon.

Problem with registration of testsuite

Cathal Curtis — Wed, 19 Sep 2018 16:52:28 -0000

I'm 7.5yrs late to this post, but I've recently come across the same problem trying to get CppUnit up and running using Cygwin on Win10.
The short answer is: before using CPPUNIT_TEST_SUITE_REGISTRATION I had to:
#include <cppunit/Portability.h>
I put it in my test.cpp file just before I included test.h

My explanation is as follows:
If you #include <cppunit/extensions/HelperMacros.h> and if you follow the files included within HelperMacros.h, you will include a file called cppunit/Portability.h.
In or around line 120 you'll see # define CPPUNIT_NS CppUnit

Now if we deconstruct (or substitute) the macros in
CPPUNIT_TEST_SUITE_REGISTRATION( ActionManualDrive_test );
we would get something like:
//static CPPUNIT_NS::AutoRegisterSuite< ActionManualDrive_test > CPPUNIT_MAKE_UNIQUE_NAME(autoRegisterRegistry__ );

I can subsitute 'anyAuldName' for the CPPUNIT_MAKE_UNIQUE_NAME macro, since it's job is to generate a unique name:
//static CPPUNIT_NS::AutoRegisterSuite< ActionManualDrive_test > anyAuldName;

CPPUNIT_NS as we say was defined as CppUnit in Portability.h:
//static CppUnit::AutoRegisterSuite< ActionManualDrive_test > anyAuldName;
But the compiler is still complaining. What it isn't exactly saying is that it doesn't know what CppUnit is.

So, without #including <cppunit/Portability.h> the compiler doesn't know what CPPUNIT_NS is.
At this point in my code the compiler still doesn't know CppUnit is a namespace. Perhaps by luck or naivety my test.h file has the following include tree:
test.h: #include <cppunit/extensions/HelperMacros.h>
HelperMacros.h: #include <cppunit/TestCaller.h>
TestCaller.h: calls CPPUNIT_NS_BEGIN, which is defined in Portability.h as:
# define CPPUNIT_NS_BEGIN namespace CppUnit {
And this is the point where the compiler learns about a namespace called CppUnit.

It took me several hours to get to the bottom of this.
I hope it helps someone else.
Cathal.

cppunit - makefile configuration: having two compilers - cmake alternative

Andre nozze — Fri, 15 Jul 2016 06:17:25 -0000

The answer at point "b" also interesting to me (Is there a "standard" cmake?)

Thanks!

Migrate to GitHub

Jan Niklas Hasse — Tue, 05 Jul 2016 14:40:22 -0000

Hi!

It seems that there isn't a lot of development on CppUnit in the recent years. I think a move to GitHub would help :)

I've already migrated the SVN repo: https://github.com/jhasse/cppunit

But it would be great, if the issues can also be migrated over. I've found this script that seems to be able to do that: https://github.com/cmungall/gosf2github

Can someone with admin reights export the tickets on sourceforge? https://sourceforge.net/p/cppunit/admin/export

Best regards
Jan Niklas

cppunit - makefile configuration: having two compilers - cmake alternative

Miguel Arnedo — Sat, 28 May 2016 03:26:54 -0000

I would like to add cppunit tests to my source code. Running under Ubuntu. 2 questions:

a) I have to make cppunit using a compiler that is located under mnt//gcc/c++-concept-branch (instead of the local one at ust/bin). Any tips of how to force make to look for it, might be by modifying the makefile ?

b) Is there a "standard" cmake in order to build cppunit, insted of using the makefile ?

Thanks in advance !

Test suite setup and teardown

Darshan — Tue, 01 Sep 2015 14:00:12 -0000

I am trying to write a setup() and teardown() function for the entire suite which are supposedly run only once (not the test fixture setup/teardown ones which run for each of the test case).

I googled and found somewhere that CPPUNIT_TEST_SUITE_SETUP() and CPPUNIT_TEST_SUITE_TEARDOWN() can be used to register my methods. But I am not able to find the definitions of these macros anywhere. I am using 1.12.1 and are these not supported ?

Are there any other solutions for my requirement ?

Recent posts to Discussion

CppUnit Code coverage Tool

Unable to link CPPunit test

Unable to link CPPunit test

Problem with registration of testsuite

Problem with registration of testsuite

cppunit - makefile configuration: having two compilers - cmake alternative

Migrate to GitHub

cppunit - makefile configuration: having two compilers - cmake alternative

Test suite setup and teardown