CppUnit project page | FAQ | CppUnit home page

- Main Page
- Related Pages
- Modules
- Namespaces
- Classes
- Files

- Class List
- Class Index
- Class Hierarchy
- Class Members

Class Hierarchy
This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 1 2 3 4 5]

Asserter | A set of functions to help writing assertion macros.Here is an example of assertion, a simplified version of the actual assertion implemented in examples/cppunittest/XmlUniformiser.h:
assertion_traits< T > | Traits used by CPPUNIT_ASSERT_EQUAL()
assertion_traits< double > | Traits used by CPPUNIT_ASSERT_DOUBLES_EQUAL()
AutoRegisterRegistry | (Implementation) Automatically adds a registry into another registry
AutoRegisterSuite< TestCaseType > | (Implementation) Automatically register the test suite of the specified type
CppUnitTestPlugIn | Test plug-in interface.This class define the interface implemented by test plug-in. A pointer to that interface is returned by the function exported by the test plug-in
TestPlugInDefaultImpl | Default implementation of test plug-in interface.Override getSuiteName() to specify the suite name. Default is "All Tests"
DynamicLibraryManager | Manages dynamic libraries
exception |
Exception | Exceptions thrown by failed assertions.Exception is an exception that serves descriptive strings through its what() method
SynchronizedObject::ExclusiveZone | Locks a synchronization object in the current scope
Functor |
ProtectorChain::ProtectFunctor |
TestCaseMethodFunctor | Functor to call test case method (Implementation)
ITestRunnerDSPluginVtbl |
Message | Message associated to an Exception.A message is composed of two items:
AdditionalMessage | An additional Message for assertions.Provides a implicit constructor that takes a single string. This allow this class to be used as the message arguments in macros
MfcTestRunner | MFC test runner.Use this to launch the MFC TestRunner. Usually called from you CWinApp subclass:
Outputter | Abstract outputter to print test result summary
CompilerOutputter | Outputs a TestResultCollector in a compiler compatible format.Printing the test results in a compiler compatible format (assertion location has the same format as compiler error), allow you to use your IDE to jump to the assertion failure. Location format can be customized (see setLocationFormat() )
TextOutputter | Prints a TestResultCollector to a text stream
XmlOutputter | Outputs a TestResultCollector in XML format.Save the test result as a XML stream
PlugInManager::PlugInInfo | (INTERNAL) Information about a specific plug-in
PlugInManager | Manges TestPlugIn
PlugInParameters | Test plug-ins parameters
Protector | Protects one or more test case run
DefaultProtector | Default protector that catch all exceptions (Implementation)
ProtectorChain | Protector chain (Implementation). Implementation detail
ProtectorContext | Protector context (Implementation). Implementation detail
ProtectorGuard | Scoped protector push to TestResult
QtTestRunner | QT test runner.Here is an example of usage:
runtime_error |
DynamicLibraryManagerException | Exception thrown by DynamicLibraryManager when a failure occurs
SourceLine | Represents a source line location.Used to capture the failure location in assertion
StringTools | Tool functions to manipulate string
SynchronizedObject::SynchronizationObject | Abstract synchronization object (mutex)
SynchronizedObject | Base class for synchronized object
TestResult | Manages TestListener.A single instance of this class is used when running the test. It is usually created by the test runner (TestRunner)
TextTestResult | Holds printable test result (DEPRECATED).deprecated Use class TextTestProgressListener and TextOutputter instead
TestSuccessListener | TestListener that checks if any test case failed
TestResultCollector | Collects test result.A TestResultCollector is a TestListener which collects the results of executing a test case. It is an instance of the Collecting Parameter pattern
TextTestResult | Holds printable test result (DEPRECATED).deprecated Use class TextTestProgressListener and TextOutputter instead
Test | Base class for all test objects.All test objects should be a subclass of Test. Some test objects, TestCase for example, represent one individual test. Other test objects, such as TestSuite, are comprised of several tests
TestComposite | A Composite of Tests
TestSuite | A Composite of Tests.It runs a collection of test cases. Here is an example
TestRunner::WrappingSuite | (INTERNAL) Mutating test suite
TestDecorator | Decorator for Tests
RepeatedTest | Decorator that runs a test repeatedly
TestSetUp | Decorates a test by providing a specific setUp() and tearDown()
TestLeaf | A single test object
TestCase | A single test object
Orthodox< ClassUnderTest > |
TestCaller< Fixture > | Generate a test case from a fixture method.A test caller provides access to a test case method on a test fixture class. Test callers are useful when you want to run an individual test or add it to a suite. Test Callers invoke only one Test (i.e. test method) on one Fixture of a TestFixture
TestCaseDecorator | Decorator for Test cases
ExceptionTestCaseDecorator< ExpectedException > | Expected exception test case decorator
TestFactory | Abstract Test factory
TestFactoryRegistry | Registry for TestFactory.Notes that the registry DON'T assumes lifetime control for any registered tests anymore
TestSuiteFactory< TestCaseType > | TestFactory for TestFixture that implements a static suite() method
TestFactoryRegistryList | (INTERNAL) List of all TestFactoryRegistry
TestFailure | Record of a failed Test execution.A TestFailure collects a failed test together with the caught exception
TestFixture | Wraps a test case with setUp and tearDown methods.A TestFixture is used to provide a common environment for a set of test cases
TestCase | A single test object
TestFixtureFactory | Abstract TestFixture factory (Implementation)
TestFixtureFactory |
ConcretTestFixtureFactory< TestFixtureType > | Concret TestFixture factory (Implementation)
TestListener | Listener for test progress and result.Implementing the Observer pattern a TestListener may be registered to a TestResult to obtain information on the testing progress. Use specialized sub classes of TestListener for text output (TextTestProgressListener). Do not use the Listener for the test result output, use a subclass of Outputter instead
BriefTestProgressListener | TestListener that prints the name of each test before running it
TestSuccessListener | TestListener that checks if any test case failed
TextTestProgressListener | TestListener that show the status of each TestCase test result
TestNamer | Names a test or a fixture suite
TestPath | A List of Test representing a path to access a Test.The path can be converted to a string and resolved from a string with toString() and TestPath( Test *root, const std::string &pathAsString )
TestPlugInInterface | Abstract TestPlugIn for DLL
TestRunner | Generic test runner.The TestRunner assumes ownership of all added tests: you can not add test or suite that are local variable since they can't be deleted
TestRunner |
TextTestRunner | A text mode test runner.The test runner manage the life cycle of the added tests
TestSuiteBuilderContextBase | Context used when creating test suite in HelperMacros
TestSuiteBuilderContext< Fixture > | Type-sage context used when creating test suite in HelperMacros
XmlDocument | A XML Document
XmlElement | A XML Element
XmlOutputterHook | Hook to customize Xml output

| hosts this site. |  | Send comments to: CppUnit Developers