CppUnit is a unit testing framework module for the C++ programming language. It allows “CppUnit Documentation”. ^ Jenkins plug-in for CppUnit and other Unit Test tools; ^ fork presented as CppUnit v; ^ fork. This document gives a simple example of CppUnit. The content covers the download of CppUnit,an example of CppUnit, compilation and. Easy refactoring of code. The unit test is a form of documentation in cppunit. C++ framework. Derived from jUnit. Centered around unit testing as a concept -.

Author: Brara Arashikazahn
Country: Montenegro
Language: English (Spanish)
Genre: Sex
Published (Last): 21 June 2016
Pages: 476
PDF File Size: 16.25 Mb
ePub File Size: 20.24 Mb
ISBN: 745-8-21246-991-5
Downloads: 80471
Price: Free* [*Free Regsitration Required]
Uploader: Kelar

There are several parts of unit testing. We begin with the the test suite. C will automatically call all linked and registered TestCase classes. There are different types of asserts we can use in our pcpunit functions. We’ll call it TestCartesianComplexMath. Unit tests are code, separate and independent from the code it tests, that can be run automatically.

TestResult controller; TestResultCollector result; controller. More can be found at the Wikipedia entry or about. The function runTest is handled by the macros.

CppUnit – Wikipedia

We need some new flags at the top of the file. TestFixture is a subclass of TestCase test cases. This is but a small sample of what is available.


Since we used the helper macro for test suite registration, test. We define the rest in the.

CppUnit Documentation

All of this goes in int main. These flags will be used to tell the compiler where to find the CppUnit headers and declarations. Declare them public along with the test functions. We’ll see the importance of this name registration later. Each test a function handles a small part of the test, and combined the functions test the whole thing. TestCase TestCase has a virtual method void runTest we must override.

We also have a TestResult class which is the controller or event manager and a TestResultCollector class that listens for tests being run. If they all pass, you get an OK message.

The private variables should be created and destroyed in the respective TestFixture function.

Our tests are called from inside the runTest method. Our class will handle the basic math operations addition, subtraction, multiplication and division. It runs all the test suites and collects the results.

Our TestCase will have several instances of CartesianComplex that will be needed by all ccppunit in the test case. Some of the most common are: Our test class will extend CppUnit’s TestCase class. We’ll go over how ccppunit create each in CppUnit.


CppUnit – The Unit Testing Library

Adding these functions to the test case can be a little errorprone, but fortunately CppUnit has helper macros. We will be using the latest stable version, release 1. It is a collection of tests run together as a unit. CppUnit has a special class, called a fixture, for just this purpose.

TestFixture Make the commonly docymentation variables private.

When the tests are run, it’ll give you a message. The value a is the real part and b is the complex part. Cppuhit only change we need to make in the Makefile is the linking of the files. If one of them fails, it’ll tell you the name of the test case, the name of the source file and the line docmentation.

The test function names begin with “test”. The basic collection of tests is the TestCase class. Notice that the registration name matched the class name. First we create a suite to run the tests.