UnitTesting - Revision history

Arthurk12: Removes outdated modifications and adds others that are needed to get UnitTest++ compiling with no warnings.

2022-04-14T15:40:28Z

Removes outdated modifications and adds others that are needed to get UnitTest++ compiling with no warnings.

← Older revision		Revision as of 15:40, 14 April 2022
Line 275:		Line 275:

	But before we build, let's modify some source files (not really needed, but I prefer to have warning free compilations). These are the changes I carried out :		But before we build, let's modify some source files (not really needed, but I prefer to have warning free compilations). These are the changes I carried out :
	* ~~ReportAssert~~.~~cpp~~ : ~~#include "ReportAssert.h"~~		* DeferredTestResult.h: remove semicolon after ''UNITTEST_STDVECTOR_LINKAGE(UnitTest::DeferredTestFailure)''
	* ~~win32/TimeHelpers~~.~~cpp~~ : ~~first the m_threadHandle and then the m_startTime in the initializerlist~~		* DeferredTestReporter.h: remove semicolon after ''UNITTEST_STDVECTOR_LINKAGE(UnitTest::DeferredTestResult)''

	Next open up this project file in Code::Blocks and build the debug and release target. From now one we will only use the Release target, we go for speed ;-)		Next open up this project file in Code::Blocks and build the debug and release target. From now one we will only use the Release target, we go for speed ;-)

Arthurk12: There are new files on the UnitTest++ 2.0 version that needed to be included on the .cbp project file.

2022-04-14T15:32:53Z

There are new files on the UnitTest++ 2.0 version that needed to be included on the .cbp project file.

← Older revision		Revision as of 15:32, 14 April 2022
Line 226:		Line 226:
	<Unit filename="../UnitTest++/ReportAssert.cpp" />		<Unit filename="../UnitTest++/ReportAssert.cpp" />
	<Unit filename="../UnitTest++/ReportAssert.h" />		<Unit filename="../UnitTest++/ReportAssert.h" />
			<Unit filename="../UnitTest++/RequiredCheckException.cpp" />
			<Unit filename="../UnitTest++/RequiredCheckException.h" />
			<Unit filename="../UnitTest++/RequiredCheckTestReporter.cpp" />
			<Unit filename="../UnitTest++/RequiredCheckTestReporter.h" />
			<Unit filename="../UnitTest++/RequireMacros.h" />
	<Unit filename="../UnitTest++/Test.cpp" />		<Unit filename="../UnitTest++/Test.cpp" />
	<Unit filename="../UnitTest++/Test.h" />		<Unit filename="../UnitTest++/Test.h" />

Braulio.solano: There was still an error. src/ does not exists anymore but UnitTest++ exists instead.

2015-05-26T17:41:38Z

There was still an error. src/ does not exists anymore but UnitTest++ exists instead.

← Older revision		Revision as of 17:41, 26 May 2015
Line 193:		Line 193:
	<Add alias="All" targets="Debug;Release;Debug(linux);Release(linux);" />		<Add alias="All" targets="Debug;Release;Debug(linux);Release(linux);" />
	</VirtualTargets>		</VirtualTargets>
	<Unit filename="../AssertException.cpp" />		<Unit filename="../UnitTest++/AssertException.cpp" />
	<Unit filename="../AssertException.h" />		<Unit filename="../UnitTest++/AssertException.h" />
	<Unit filename="../CheckMacros.h" />		<Unit filename="../UnitTest++/CheckMacros.h" />
	<Unit filename="../Checks.cpp" />		<Unit filename="../UnitTest++/Checks.cpp" />
	<Unit filename="../Checks.h" />		<Unit filename="../UnitTest++/Checks.h" />
	<Unit filename="../Config.h" />		<Unit filename="../UnitTest++/Config.h" />
	<Unit filename="../CurrentTest.cpp" />		<Unit filename="../UnitTest++/CurrentTest.cpp" />
	<Unit filename="../CurrentTest.h" />		<Unit filename="../UnitTest++/CurrentTest.h" />
	<Unit filename="../DeferredTestReporter.cpp" />		<Unit filename="../UnitTest++/DeferredTestReporter.cpp" />
	<Unit filename="../DeferredTestReporter.h" />		<Unit filename="../UnitTest++/DeferredTestReporter.h" />
	<Unit filename="../DeferredTestResult.cpp" />		<Unit filename="../UnitTest++/DeferredTestResult.cpp" />
	<Unit filename="../DeferredTestResult.h" />		<Unit filename="../UnitTest++/DeferredTestResult.h" />
	<Unit filename="../ExecuteTest.h" />		<Unit filename="../UnitTest++/ExecuteTest.h" />
	<Unit filename="../MemoryOutStream.cpp" />		<Unit filename="../UnitTest++/MemoryOutStream.cpp" />
	<Unit filename="../MemoryOutStream.h" />		<Unit filename="../UnitTest++/MemoryOutStream.h" />
	<Unit filename="../Posix/SignalTranslator.cpp">		<Unit filename="../UnitTest++/Posix/SignalTranslator.cpp">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="../Posix/SignalTranslator.h">		<Unit filename="../UnitTest++/Posix/SignalTranslator.h">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="../Posix/TimeHelpers.cpp">		<Unit filename="../UnitTest++/Posix/TimeHelpers.cpp">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="../Posix/TimeHelpers.h">		<Unit filename="../UnitTest++/Posix/TimeHelpers.h">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="../ReportAssert.cpp" />		<Unit filename="../UnitTest++/ReportAssert.cpp" />
	<Unit filename="../ReportAssert.h" />		<Unit filename="../UnitTest++/ReportAssert.h" />
	<Unit filename="../Test.cpp" />		<Unit filename="../UnitTest++/Test.cpp" />
	<Unit filename="../Test.h" />		<Unit filename="../UnitTest++/Test.h" />
	<Unit filename="../TestDetails.cpp" />		<Unit filename="../UnitTest++/TestDetails.cpp" />
	<Unit filename="../TestDetails.h" />		<Unit filename="../UnitTest++/TestDetails.h" />
	<Unit filename="../TestList.cpp" />		<Unit filename="../UnitTest++/TestList.cpp" />
	<Unit filename="../TestList.h" />		<Unit filename="../UnitTest++/TestList.h" />
	<Unit filename="../TestMacros.h" />		<Unit filename="../UnitTest++/TestMacros.h" />
	<Unit filename="../TestReporter.cpp" />		<Unit filename="../UnitTest++/TestReporter.cpp" />
	<Unit filename="../TestReporter.h" />		<Unit filename="../UnitTest++/TestReporter.h" />
	<Unit filename="../TestReporterStdout.cpp" />		<Unit filename="../UnitTest++/TestReporterStdout.cpp" />
	<Unit filename="../TestReporterStdout.h" />		<Unit filename="../UnitTest++/TestReporterStdout.h" />
	<Unit filename="../TestResults.cpp" />		<Unit filename="../UnitTest++/TestResults.cpp" />
	<Unit filename="../TestResults.h" />		<Unit filename="../UnitTest++/TestResults.h" />
	<Unit filename="../TestRunner.cpp" />		<Unit filename="../UnitTest++/TestRunner.cpp" />
	<Unit filename="../TestRunner.h" />		<Unit filename="../UnitTest++/TestRunner.h" />
	<Unit filename="../TestSuite.h" />		<Unit filename="../UnitTest++/TestSuite.h" />
	<Unit filename="../TimeConstraint.cpp" />		<Unit filename="../UnitTest++/TimeConstraint.cpp" />
	<Unit filename="../TimeConstraint.h" />		<Unit filename="../UnitTest++/TimeConstraint.h" />
	<Unit filename="../TimeHelpers.h" />		<Unit filename="../UnitTest++/TimeHelpers.h" />
	<Unit filename="../UnitTest++.h" />		<Unit filename="../UnitTest++/UnitTest++.h" />
	<Unit filename="../Win32/TimeHelpers.cpp">		<Unit filename="../UnitTest++/Win32/TimeHelpers.cpp">
	<Option target="Debug" />		<Option target="Debug" />
	<Option target="Release" />		<Option target="Release" />
	</Unit>		</Unit>
	<Unit filename="../Win32/TimeHelpers.h">		<Unit filename="../UnitTest++/Win32/TimeHelpers.h">
	<Option target="Debug" />		<Option target="Debug" />
	<Option target="Release" />		<Option target="Release" />
	</Unit>		</Unit>
	<Unit filename="../XmlTestReporter.cpp" />		<Unit filename="../UnitTest++/XmlTestReporter.cpp" />
	<Unit filename="../XmlTestReporter.h" />		<Unit filename="../UnitTest++/XmlTestReporter.h" />
	<Extensions>		<Extensions>
	<envvars />		<envvars />

Braulio.solano: The structure on the code has changed. The code is no longer in a src/ directory. I have erased it from the project file for UnitTest++ compilation.

2015-04-17T16:28:16Z

The structure on the code has changed. The code is no longer in a src/ directory. I have erased it from the project file for UnitTest++ compilation.

← Older revision		Revision as of 16:28, 17 April 2015
Line 193:		Line 193:
	<Add alias="All" targets="Debug;Release;Debug(linux);Release(linux);" />		<Add alias="All" targets="Debug;Release;Debug(linux);Release(linux);" />
	</VirtualTargets>		</VirtualTargets>
	<Unit filename="..~~/src~~/AssertException.cpp" />		<Unit filename="../AssertException.cpp" />
	<Unit filename="..~~/src~~/AssertException.h" />		<Unit filename="../AssertException.h" />
	<Unit filename="..~~/src~~/CheckMacros.h" />		<Unit filename="../CheckMacros.h" />
	<Unit filename="..~~/src~~/Checks.cpp" />		<Unit filename="../Checks.cpp" />
	<Unit filename="..~~/src~~/Checks.h" />		<Unit filename="../Checks.h" />
	<Unit filename="..~~/src~~/Config.h" />		<Unit filename="../Config.h" />
	<Unit filename="..~~/src~~/CurrentTest.cpp" />		<Unit filename="../CurrentTest.cpp" />
	<Unit filename="..~~/src~~/CurrentTest.h" />		<Unit filename="../CurrentTest.h" />
	<Unit filename="..~~/src~~/DeferredTestReporter.cpp" />		<Unit filename="../DeferredTestReporter.cpp" />
	<Unit filename="..~~/src~~/DeferredTestReporter.h" />		<Unit filename="../DeferredTestReporter.h" />
	<Unit filename="..~~/src~~/DeferredTestResult.cpp" />		<Unit filename="../DeferredTestResult.cpp" />
	<Unit filename="..~~/src~~/DeferredTestResult.h" />		<Unit filename="../DeferredTestResult.h" />
	<Unit filename="..~~/src~~/ExecuteTest.h" />		<Unit filename="../ExecuteTest.h" />
	<Unit filename="..~~/src~~/MemoryOutStream.cpp" />		<Unit filename="../MemoryOutStream.cpp" />
	<Unit filename="..~~/src~~/MemoryOutStream.h" />		<Unit filename="../MemoryOutStream.h" />
	<Unit filename="..~~/src~~/Posix/SignalTranslator.cpp">		<Unit filename="../Posix/SignalTranslator.cpp">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="..~~/src~~/Posix/SignalTranslator.h">		<Unit filename="../Posix/SignalTranslator.h">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="..~~/src~~/Posix/TimeHelpers.cpp">		<Unit filename="../Posix/TimeHelpers.cpp">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="..~~/src~~/Posix/TimeHelpers.h">		<Unit filename="../Posix/TimeHelpers.h">
	<Option target="Debug(linux)" />		<Option target="Debug(linux)" />
	<Option target="Release(linux)" />		<Option target="Release(linux)" />
	</Unit>		</Unit>
	<Unit filename="..~~/src~~/ReportAssert.cpp" />		<Unit filename="../ReportAssert.cpp" />
	<Unit filename="..~~/src~~/ReportAssert.h" />		<Unit filename="../ReportAssert.h" />
	<Unit filename="..~~/src~~/Test.cpp" />		<Unit filename="../Test.cpp" />
	<Unit filename="..~~/src~~/Test.h" />		<Unit filename="../Test.h" />
	<Unit filename="..~~/src~~/TestDetails.cpp" />		<Unit filename="../TestDetails.cpp" />
	<Unit filename="..~~/src~~/TestDetails.h" />		<Unit filename="../TestDetails.h" />
	<Unit filename="..~~/src~~/TestList.cpp" />		<Unit filename="../TestList.cpp" />
	<Unit filename="..~~/src~~/TestList.h" />		<Unit filename="../TestList.h" />
	<Unit filename="..~~/src~~/TestMacros.h" />		<Unit filename="../TestMacros.h" />
	<Unit filename="..~~/src~~/TestReporter.cpp" />		<Unit filename="../TestReporter.cpp" />
	<Unit filename="..~~/src~~/TestReporter.h" />		<Unit filename="../TestReporter.h" />
	<Unit filename="..~~/src~~/TestReporterStdout.cpp" />		<Unit filename="../TestReporterStdout.cpp" />
	<Unit filename="..~~/src~~/TestReporterStdout.h" />		<Unit filename="../TestReporterStdout.h" />
	<Unit filename="..~~/src~~/TestResults.cpp" />		<Unit filename="../TestResults.cpp" />
	<Unit filename="..~~/src~~/TestResults.h" />		<Unit filename="../TestResults.h" />
	<Unit filename="..~~/src~~/TestRunner.cpp" />		<Unit filename="../TestRunner.cpp" />
	<Unit filename="..~~/src~~/TestRunner.h" />		<Unit filename="../TestRunner.h" />
	<Unit filename="..~~/src~~/TestSuite.h" />		<Unit filename="../TestSuite.h" />
	<Unit filename="..~~/src~~/TimeConstraint.cpp" />		<Unit filename="../TimeConstraint.cpp" />
	<Unit filename="..~~/src~~/TimeConstraint.h" />		<Unit filename="../TimeConstraint.h" />
	<Unit filename="..~~/src~~/TimeHelpers.h" />		<Unit filename="../TimeHelpers.h" />
	<Unit filename="..~~/src~~/UnitTest++.h" />		<Unit filename="../UnitTest++.h" />
	<Unit filename="..~~/src~~/Win32/TimeHelpers.cpp">		<Unit filename="../Win32/TimeHelpers.cpp">
	<Option target="Debug" />		<Option target="Debug" />
	<Option target="Release" />		<Option target="Release" />
	</Unit>		</Unit>
	<Unit filename="..~~/src~~/Win32/TimeHelpers.h">		<Unit filename="../Win32/TimeHelpers.h">
	<Option target="Debug" />		<Option target="Debug" />
	<Option target="Release" />		<Option target="Release" />
	</Unit>		</Unit>
	<Unit filename="..~~/src~~/XmlTestReporter.cpp" />		<Unit filename="../XmlTestReporter.cpp" />
	<Unit filename="..~~/src~~/XmlTestReporter.h" />		<Unit filename="../XmlTestReporter.h" />
	<Extensions>		<Extensions>
	<envvars />		<envvars />

LETARTARE: /* Unit Test frameworks */

2015-02-02T09:49:27Z

Unit Test frameworks

← Older revision		Revision as of 09:49, 2 February 2015
Line 39:		Line 39:
	When writing unit tests, one will create a lot of similar code. Because unit tests are nothing more then little programs, several tasks will be repeated: (1)setting up the test environment; (2)create your class; (3)call a method; (4)verify its result; (5)write out an error message - preferably specifying the wrong outcome - when the test fails; and (6) what the expected result is.		When writing unit tests, one will create a lot of similar code. Because unit tests are nothing more then little programs, several tasks will be repeated: (1)setting up the test environment; (2)create your class; (3)call a method; (4)verify its result; (5)write out an error message - preferably specifying the wrong outcome - when the test fails; and (6) what the expected result is.
	All these repetitive chores are taken care of by the frame work so the developer can focus on the real code of the test.		All these repetitive chores are taken care of by the frame work so the developer can focus on the real code of the test.
	This document will use a small but very effective framework for the C++ language. It is called UnitTest++. It's homepage is at : [~~http~~://unittest-cpp~~.sourceforge.net~~/ UnitTest++].		This document will use a small but very effective framework for the C++ language. It is called UnitTest++. It's homepage is at : [https://github.com/unittest-cpp/unittest-cpp/ UnitTest++].
	You can download it directly at this [~~http~~://~~sourceforge~~.~~net/projects~~/unittest-cpp~~/files/UnitTest%2B%2B/1.4~~/unittest-cpp~~-1.4~~.zip~~/download link~~]. At the time of writing the latest version is 1.4.		You can download it directly at this [https://github.com/unittest-cpp/unittest-cpp/archive/master.zip]. At the time of writing the latest version is 1.4.


	== Setup our environment ==		== Setup our environment ==

Jareyes409 at 13:58, 15 February 2013

2013-02-15T13:58:39Z

← Older revision		Revision as of 13:58, 15 February 2013
Line 16:		Line 16:

	== Why Unit Testing ==		== Why Unit Testing ==
	~~Well we write~~ code that implements some functionality. ~~We need a~~ way to check and prove that the implementation is correct. Therefor ~~we need~~ tests. ~~We need tests on~~ the application level~~, at~~ the integration level of different components, classes, interfaces~~. But we also need tests for the smallest building blocks, the units.~~		When code is written that implements some functionality. A way to check and prove that the implementation is correct is needed. Therefor, tests are needed. Tests are needed at different levels :
	~~We also want these tests to run very quickly. That way we can run the tests often, manually or automated.~~		* the application level; and
	~~These tests will also be our safeguards during refactoring of the code, extending the code or whatever maintenance tasks we carry out on the code.~~		* the integration level of different components, classes, and interfaces.
	These tests will also make us think of how our class, method, ... will be used. Since the test can be seen as a user of our code. Thanks to this, thinking about the tests before implementing the functionality can help us in the design : emergent design.
	It will help us to avoid creating big classes, complex functions. We will only write the methods that are really needed, and no methods that we think might (n)ever be useful in the future. We are no good future tellers ! Those 'might be needed' methods and their tests are just a waste of time. Extending, refactoring will be done when it is actually needed, and at that time we have our unit tests to ensure we don't break any existing code.

	Other times to add new unit ~~tests are~~ typically when a bug is discovered. ~~Write~~ a unit test to reproduce the bug, fix the code, and from now on the new unit test will watch ~~your~~ back so the bug won't reappear.		But tests are also needed for the smallest building blocks, the units. These tests need to run very quickly. Thus, the tests can be run often - manually or automated. These tests will also be our safeguards during refactoring, extending, or maintaining the code.
			These tests encourage the programmer to think of the use of the class, method, or whatever unit because the test can be seen as a user of our code. Thanks to this process, thinking about the tests before implementing the functionality can help the programmer in the design : emergent design.
			It will help the programmer to avoid creating big classes and complex functions. The programmer will only write the methods that are really needed, and no methods that the programmer thinks might ever - or never - be useful in the future. Programmers are not good future tellers! Those 'might be needed' methods and their tests are simply a waste of time. Extending and refactoring will be done when it is actually needed, and at that time the programmer have unit tests to ensure they don't break any existing code.

			Other times when a programmer might add a new unit test is - typically - when a bug is discovered. The programmer will: (1)write a unit test to reproduce the bug; (2) fix the code; and (3) from now on the new unit test will watch the programmer's back so the bug won't reappear.

	Unit test are also a good place of documentation. The little tests show how the class or method is used.		Unit test are also a good place of documentation. The little tests show how the class or method is used.
Line 35:		Line 37:

	== Unit Test frameworks ==		== Unit Test frameworks ==
	When writing unit tests, one will create a lot of similar code. ~~Since~~ unit tests are nothing more then little programs, several tasks will be repeated, setting up the test environment, create your class, call a method, verify ~~it's~~ result, write out an error message ~~when the test fails,~~ preferably specifying ~~what~~ the wrong outcome ~~was,~~ and what the expected result is.		When writing unit tests, one will create a lot of similar code. Because unit tests are nothing more then little programs, several tasks will be repeated: (1)setting up the test environment; (2)create your class; (3)call a method; (4)verify its result; (5)write out an error message - preferably specifying the wrong outcome - when the test fails; and (6) what the expected result is.
	All these repetitive chores are taken care of by the frame work so the developer can focus on the real code of the test.		All these repetitive chores are taken care of by the frame work so the developer can focus on the real code of the test.
	This document will use a small but very effective framework for the C++ language. It is called UnitTest++. It's homepage is at : [http://unittest-cpp.sourceforge.net/ UnitTest++].		This document will use a small but very effective framework for the C++ language. It is called UnitTest++. It's homepage is at : [http://unittest-cpp.sourceforge.net/ UnitTest++].

Killerbot: /* LeapYear-Step2 */

2010-07-22T09:06:19Z

LeapYear-Step2

← Older revision		Revision as of 09:06, 22 July 2010
Line 443:		Line 443:
	</source>		</source>

	At least now it compiles, but it doesn't link yet. Duh~~, that~~ because we don't have an implementation yet.		At least now it compiles, but it doesn't link yet. Duh ! That's because we don't have an implementation yet.
	Time to provide the bare minimum of code to make the test pass.		Time to provide the bare minimum of code to make the test pass.
	So we change the LeapYear.cpp into :		So we change the LeapYear.cpp into :

Killerbot: /* Why Unit Testing */

2010-07-22T09:03:45Z

Why Unit Testing

← Older revision		Revision as of 09:03, 22 July 2010
Line 17:		Line 17:
	== Why Unit Testing ==		== Why Unit Testing ==
	Well we write code that implements some functionality. We need a way to check and prove that the implementation is correct. Therefor we need tests. We need tests on the application level, at the integration level of different components, classes, interfaces. But we also need tests for the smallest building blocks, the units.		Well we write code that implements some functionality. We need a way to check and prove that the implementation is correct. Therefor we need tests. We need tests on the application level, at the integration level of different components, classes, interfaces. But we also need tests for the smallest building blocks, the units.
	We also ~~wans~~ these tests to run very quickly. That way we can run the tests often, manually or automated.		We also want these tests to run very quickly. That way we can run the tests often, manually or automated.
	These tests will also be our safeguards during refactoring of the code, extending the code or whatever maintenance tasks we carry out on the code.		These tests will also be our safeguards during refactoring of the code, extending the code or whatever maintenance tasks we carry out on the code.
	These tests will also make us think of how our class, method, ... will be used. Since the test can be seen as a user of our code. Thanks to this, thinking about the tests before implementing the functionality can help us in the design : emergent design.		These tests will also make us think of how our class, method, ... will be used. Since the test can be seen as a user of our code. Thanks to this, thinking about the tests before implementing the functionality can help us in the design : emergent design.

Killerbot: /* LeapYear-Step3 */

2010-07-22T09:02:55Z

LeapYear-Step3

← Older revision		Revision as of 09:02, 22 July 2010
Line 460:		Line 460:

	== LeapYear-Step3 ==		== LeapYear-Step3 ==
	~~Anyone having~~ the feeling we are cheating. Well the user does not know how we wrote our code on the inside. So just to be sure the user (we) adds the following test, ending up in :		Does anyone have the feeling we are cheating? Well the user does not know how we wrote our code on the inside. So just to be sure the user (we) adds the following test, ending up in :

	<source lang="cpp">		<source lang="cpp">

Killerbot: /* Increase the user experience */

2010-07-22T09:02:08Z

Increase the user experience

← Older revision		Revision as of 09:02, 22 July 2010
Line 631:		Line 631:

	Well, didn't we say life is great, Code::Blocks and UnitTest++ to the rescue. The error/warning output of the framework is in the gcc format. That means Code::Blocks can parse it.		Well, didn't we say life is great, Code::Blocks and UnitTest++ to the rescue. The error/warning output of the framework is in the gcc format. That means Code::Blocks can parse it.
	One restriction Code::Blocks can parse it during the 'build process'. But currently the build process stops after the unit test executable is ~~build~~, and only then we run the test executable (manually).		One restriction Code::Blocks can parse it during the 'build process'. But currently the build process stops after the unit test executable is built, and only then we run the test executable (manually).
	Solution have Code::Blocks run the test executable as a post-build step. Pre-build and post-build steps are part of the build process !		Solution have Code::Blocks run the test executable as a post-build step. Pre-build and post-build steps are part of the build process !
	Important consequence : if you want to debug something, the debugger will only kick off after Code::Blocks was able to carry out a successful build (including the pre/post builds steps). Therefor it is not wise to have the unit test executable being carried out as a post-build step of the 'Debug' target. But as a post-build step of the Release target, our goal is met.		Important consequence : if you want to debug something, the debugger will only kick off after Code::Blocks was able to carry out a successful build (including the pre/post builds steps). Therefor it is not wise to have the unit test executable being carried out as a post-build step of the 'Debug' target. But as a post-build step of the Release target, our goal is met.