CppUnit project page FAQ

Class Hierarchy

Go to the graphical class hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 12345]
 CAsserterA 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:
 Cassertion_traits< T >Traits used by CPPUNIT_ASSERT_EQUAL()
 Cassertion_traits< double >Traits used by CPPUNIT_ASSERT_DOUBLES_EQUAL()
 CAutoRegisterRegistry(Implementation) Automatically adds a registry into another registry
 CAutoRegisterSuite< TestCaseType >(Implementation) Automatically register the test suite of the specified type
 CCppUnitTestPlugInTest 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
 CTestPlugInDefaultImplDefault implementation of test plug-in interface.Override getSuiteName() to specify the suite name. Default is "All Tests"
 CDynamicLibraryManagerManages dynamic libraries
 Cexception
 CExceptionExceptions thrown by failed assertions.Exception is an exception that serves descriptive strings through its what() method
 CSynchronizedObject::ExclusiveZoneLocks a synchronization object in the current scope
 CFunctor
 CProtectorChain::ProtectFunctor
 CTestCaseMethodFunctorFunctor to call test case method (Implementation)
 CITestRunnerDSPluginVtbl
 CMessageMessage associated to an Exception.A message is composed of two items:
 CAdditionalMessageAn 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
 CMfcTestRunnerMFC test runner.Use this to launch the MFC TestRunner. Usually called from you CWinApp subclass:
 COutputterAbstract outputter to print test result summary
 CCompilerOutputterOutputs 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() )
 CTextOutputterPrints a TestResultCollector to a text stream
 CXmlOutputterOutputs a TestResultCollector in XML format.Save the test result as a XML stream
 CPlugInManager::PlugInInfo(INTERNAL) Information about a specific plug-in
 CPlugInManagerManges TestPlugIn
 CPlugInParametersTest plug-ins parameters
 CProtectorProtects one or more test case run
 CDefaultProtectorDefault protector that catch all exceptions (Implementation)
 CProtectorChainProtector chain (Implementation). Implementation detail
 CProtectorContextProtector context (Implementation). Implementation detail
 CProtectorGuardScoped protector push to TestResult
 CQtTestRunnerQT test runner.Here is an example of usage:
 Cruntime_error
 CDynamicLibraryManagerExceptionException thrown by DynamicLibraryManager when a failure occurs
 CSourceLineRepresents a source line location.Used to capture the failure location in assertion
 CStringToolsTool functions to manipulate string
 CSynchronizedObject::SynchronizationObjectAbstract synchronization object (mutex)
 CSynchronizedObjectBase class for synchronized object
 CTestResultManages TestListener.A single instance of this class is used when running the test. It is usually created by the test runner (TestRunner)
 CTextTestResultHolds printable test result (DEPRECATED).deprecated Use class TextTestProgressListener and TextOutputter instead
 CTestSuccessListenerTestListener that checks if any test case failed
 CTestResultCollectorCollects 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
 CTextTestResultHolds printable test result (DEPRECATED).deprecated Use class TextTestProgressListener and TextOutputter instead
 CTestBase 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
 CTestCompositeA Composite of Tests
 CTestSuiteA Composite of Tests.It runs a collection of test cases. Here is an example
 CTestRunner::WrappingSuite(INTERNAL) Mutating test suite
 CTestDecoratorDecorator for Tests
 CRepeatedTestDecorator that runs a test repeatedly
 CTestSetUpDecorates a test by providing a specific setUp() and tearDown()
 CTestLeafA single test object
 CTestCaseA single test object
 COrthodox< ClassUnderTest >
 CTestCaller< 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
 CTestCaseDecoratorDecorator for Test cases
 CExceptionTestCaseDecorator< ExpectedException >Expected exception test case decorator
 CTestFactoryAbstract Test factory
 CTestFactoryRegistryRegistry for TestFactory.Notes that the registry DON'T assumes lifetime control for any registered tests anymore
 CTestSuiteFactory< TestCaseType >TestFactory for TestFixture that implements a static suite() method
 CTestFactoryRegistryList(INTERNAL) List of all TestFactoryRegistry
 CTestFailureRecord of a failed Test execution.A TestFailure collects a failed test together with the caught exception
 CTestFixtureWraps a test case with setUp and tearDown methods.A TestFixture is used to provide a common environment for a set of test cases
 CTestCaseA single test object
 CTestFixtureFactoryAbstract TestFixture factory (Implementation)
 CTestFixtureFactory
 CConcretTestFixtureFactory< TestFixtureType >Concret TestFixture factory (Implementation)
 CTestListenerListener 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
 CBriefTestProgressListenerTestListener that prints the name of each test before running it
 CTestSuccessListenerTestListener that checks if any test case failed
 CTextTestProgressListenerTestListener that show the status of each TestCase test result
 CTestNamerNames a test or a fixture suite
 CTestPathA 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 )
 CTestPlugInInterfaceAbstract TestPlugIn for DLL
 CTestRunnerGeneric 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
 CTestRunner
 CTextTestRunnerA text mode test runner.The test runner manage the life cycle of the added tests
 CTestSuiteBuilderContextBaseContext used when creating test suite in HelperMacros
 CTestSuiteBuilderContext< Fixture >Type-sage context used when creating test suite in HelperMacros
 CXmlDocumentA XML Document
 CXmlElementA XML Element
 CXmlOutputterHookHook to customize Xml output

Send comments to:
CppUnit Developers