Recent changes to feature-requests

Make TestFixture getter const

Dylan Ilsley — Thu, 29 Feb 2024 10:19:12 -0000

Currently currentTestName() is no const, this has a ripple effect for any functions that override it as well.

Please consider a CPPUNIT_ASSERT_LAMBDA macro

Chris Tapley — Wed, 31 May 2017 01:42:28 -0000

Hello,

It would be handy to have a CPPUNIT_ASSERT_LAMBDA(condition, lambda) macro where the lambda is only called if the condition is false. This makes extracting error messages from objects easier and the test code simpler.

#if (defined(_MSC_VER) && _MSC_VER >= 1800) || (defined(__cplusplus) && __cplusplus > 199711L)
/** Assertion with a user specified lamda.
* \ingroup Assertions
* \param condition If this condition evaluates to \c false then the
*                  test failed.
* \param lambda Message detail is generated when needed and reported in
*  diagnostic if \a condition evaluates to \c false.
*/
#define CPPUNIT_ASSERT_LAMBDA(condition, lambda)                                        \
  ( CPPUNIT_NS::Asserter::failIf( !(condition),                                         \
                                  CPPUNIT_NS::Message( "assertion failed",              \
                                                       "Expression: "                   \
                                                       #condition,                      \
                                                       !(condition) ? lambda() : "" ),  \
                                  CPPUNIT_SOURCELINE() ) )
#endif

Compilation of tests with g++ -std=c++11 can warn about auto_ptr

Ron Fox — Mon, 10 Nov 2014 18:35:32 -0000

If I compile a file with more than one class derived from CppUnit::TestFixture under gcc/g++ 4.7.2 (Debian 4.7.2-5) on Debian Wheezy (cppunit-1.12-1). The CPPUNIT_TEST_SUITE_END macro invocation in all but the first class will warn that auto_ptr is deprecated.

Workaround choice of:
1. Break up compilation units so that only one test fixture is in each file.
2. Add -Wdeprecated-declarations to the compilation flags.

Desired solution:
Conditionally use unique_ptr or shared_ptr as appropriate if the compilation standard level is at c++-11.0 or higher(?) (checking the value of __cplusplus).

#57 CPPUnit Test Run Report XML to HTML Report similar to Junit or CUnit

Bitwise — Mon, 06 Oct 2014 19:01:05 -0000

The feature you want is already implemented. I have Ubuntu, but do not develop on it. As a Windows developer, here is a script I use during my build process to create html output. You will need to translate to your environment. The output file I generate here is "UnitTestResults.xml", which is html internally. You can probably pick a different name. :-)

@echo off

setlocal enabledelayedexpansion

@rem Expected parameters
@rem
@rem param1: location of targets for the solution (not the project)
@rem param2: [optional] if non-blank, the unit test target (else all we can find)

@rem Determine if we are running debug or release (or other)
cd %1
set where=%cd%
set where=%where:Debug=xx%
set build=Debug
if "%cd%" == "%where%" set build=Release

@rem identify all files ending in _test.dll and _unittest.dll
set params=%2
if "%params%" NEQ "" goto :skipparams
dir /b _test.dll > filelist.tmp 2> NUL
dir /b _unittest.dll >> filelist.tmp 2> NUL

for /f "usebackq delims=" %%a in (filelist.tmp) do set params=!params! %%a
del filelist.tmp
:skipparams

goto %build%

:debug
@rem del /Q "UnitTestResults.xml"
echo DllPlugInTesterd_dll.exe -c -x UnitTestResults.xml -s UnitTestReport.xsl clockerplugind.dll %params%
DllPlugInTesterd_dll.exe -c -x UnitTestResults.xml -s UnitTestReport.xsl clockerplugind.dll %params%
goto :EOF

:release
@rem del /Q "UnitTestResults.xml"
echo DllPlugInTester_dll.exe -c -x UnitTestResults.xml -s UnitTestReport.xsl clockerplugin.dll %params%
DllPlugInTester_dll.exe -c -x UnitTestResults.xml -s UnitTestReport.xsl clockerplugin.dll %params%
goto :EOF

:EOF

CPPUnit Test Run Report XML to HTML Report similar to Junit or CUnit

stl — Sat, 20 Sep 2014 15:28:05 -0000

Hi,
I am QA guy and beginner in C,C++ unit testing.
Please help.
Working on Ubuntu 14.04 64 bit.
Created sample cpp class and a corresponding Test.cpp.

Have been able to create the .xml output file for the CPPUnit tests run using XmlOutputter.
But how to get the HTML report using this xml, is there any predefined XSL, DTD or something like that (as in case of CUnit), so that if these files are there in the same directory as the CPPUnit generated XML file then it would simply show an HTML report.
OR
Some way by which ANT can be used to generate the HTML report similar to JUnit.
Referred

39 XSLT for compatibility with Ant junit xml formatter

But could not understand well as variable and paths assumed I am not sure of and new to ANT build.xml etc. too.
It is in closed status and the guideline is given at a high level, if someone can help
1 - provide the XSLT, DTD or whatever that needs to be just copied to the folder where CPPUnit generated test run report XML is there and the HTML would get displayed
OR
2 - build.xml with the required variables (to be able to understand the directories and paths assumed in the example given) and targets that can be actually used with ANT to generate JUnit like report

Appreciate your patience to read through.
Thanks in advance

#39 parameterized fixture

fussel4711 — Wed, 26 Feb 2014 07:49:32 -0000

I've implemented some macros aiding to define parameterized CppUnit tests.

With this solution you just need to replace the old macros CPPUNIT_TEST_SUITE and CPPUNIT_TEST_SUITE_END within the class's header file:

CPPUNIT_PARAMETERIZED_TEST_SUITE(<TestSuiteClass>, <ParameterType>);
/*
 * Put plain old tests here.
 */ 
CPPUNIT_PARAMETERIZED_TEST_SUITE_END();

In the implementation file you need to replace the old CPPUNIT_TEST_SUITE_REGISTRATION macro with:

CPPUNIT_PARAMETERIZED_TEST_SUITE_REGISTRATION (<TestSuiteClass>, <ParameterType>)

These macros require you to implement the methods:

static std::vector parameters();
void testWithParameter(ParameterType& parameter);

parameters(): Provides a vector with the parameters.
testWithParameter(...): Is called for each parameter. This is where you implement your parameterized test.

A detailed explanation can be found here: http://brain-child.de/engineering/parameterizing-cppunit-tests

The german version can be found here: http://brain-child.de/engineering/parametrierbare-tests-cppunit

I would appreciate if the CppUnit team will integrate my work into the CppUnit framework. In this case it would be nice if you mention the source within the source code and documentation ;)

Make TextProgressListener flush standard output after writes

Calder — Wed, 01 Dec 2010 22:38:38 -0000

Adding the following line at the end of startTest():
stdCOut().flush();
makes the progress indicator actually useful. As it stands, it doesn't actually indicate anything because nothing appears in standard out until a newline is written there.

Fix output for temmplate classes

Enki — Mon, 16 Aug 2010 20:14:28 -0000

Hi,

The output for the brackets in template class names and the scope operator does not work properly. For an example please see the help-forum thread http://sourceforge.net/projects/cppunit/forums/forum/37108/topic/3807203. I suspect the helper macros to be the cause of the problem.

It would be nice, if you could fix this.
Thanks,
jg

Add Setup, Teardown method for fixture

RiouxYz — Wed, 10 Jun 2009 20:11:58 -0000

In some case it will be useful to have a setup and teardown method for fixture. This could speed up execution of the test if I generate const object only once for all the fixture. Presently they waste time to regenerate object for each test.

Win64 build

nik — Wed, 03 Dec 2008 09:08:11 -0000

I am working on building the source of CPPunit 1.12.1 version on Windows 64 XP (x64) in MS Visual Studio 2005 (V8). However, a couple of issues appeared during building listed below:

1. In Configuration Manager of the Build menu option, I needed to select x64 as the Active solution platform since the active solution was set to Win32. This is expected since Win64 is supposedly not supported.

2. In the Preprocessor Definitions option in the project C/C++ configuration properties, I changed WIN32 to WIN64 since I was building for WIN64. Now this step is not mandatory since the projects build for Win32 but I felt it would be appropriate that way.

3. Some erros occured in some of the projects while others occurred in all projects apart from 'cppunit' and 'cppunit_dll':

a) .\DynamicWindow\cdxCDynamicDialog.cpp(30) : error C2440: 'static_cast' : cannot convert from 'void (__cdecl cdxCDynamicDialog::* )(UINT)' to 'void (__cdecl CWnd::* )(UINT_PTR)' ---> I changed UINT to UINT_PTR in the OnTimer function and the error was corrected.

b) .\MsDevCallerListCtrl.cpp(67) : error C3505: cannot load type library '{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}'
.\MsDevCallerListCtrl.cpp(67) : fatal error C1104: fatal error importing libid: '80cc9f66-e7d8-4ddd-85b6-d9e6cd0e93e2'

c)...\cppunit-1.12.1\src\msvc6\dsplugin\stdafx.h(12) : fatal error C1189: #error : This add-in is for VC++ 6.0 only

I therefore built the 'cppunit' and 'cppunit_dll projects only. Most of these erros I guess are due to the fact that Win64 is not supported. Is there a temporary solution available at the moment which can be used to build the CPPUnitLibraries solution. If not, as one user already asked, when can we expect a solution for Win64.

Thanks in advance.