I will present a lecture about C++ Unit Tests and need to explain the features of CPPUnit,
but I didn't understood some of the features and didn't realized how to create a example:
The features I need some help/explanation are:
* Hierarchical test fixture support
* Test registry to reduce recompilation need
* Test plug-in for faster compile/test cycle (self testable dynamic library)
* Protector to encapsulate test execution (allow capture of exception not derived from std::exception)
Maybe is just too obvious, but if someone point the correlation it will be clear.
Thank you.
List of all features:
Features:
* XML output with hooks for additional data (XSL format avaliable in release 1.10.2 needs some FiXing)
* Compiler-like text output to integrate with an IDE
* Helper macros for easier test suite declaration
* Hierarchical test fixture support
* Test registry to reduce recompilation need
* Test plug-in for faster compile/test cycle (self testable dynamic library)
* Protector to encapsulate test execution (allow capture of exception not derived from std::exception)
* MfcTestRunner
* QtTestRunner, a Qt based graphic test runner
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Need some correlation between the features and a example of use.
I will present a lecture about C++ Unit Tests and need to explain the features of CPPUnit,
but I didn't understood some of the features and didn't realized how to create a example:
The features I need some help/explanation are:
* Hierarchical test fixture support
* Test registry to reduce recompilation need
* Test plug-in for faster compile/test cycle (self testable dynamic library)
* Protector to encapsulate test execution (allow capture of exception not derived from std::exception)
Maybe is just too obvious, but if someone point the correlation it will be clear.
Thank you.
List of all features:
Features:
* XML output with hooks for additional data (XSL format avaliable in release 1.10.2 needs some FiXing)
* Compiler-like text output to integrate with an IDE
* Helper macros for easier test suite declaration
* Hierarchical test fixture support
* Test registry to reduce recompilation need
* Test plug-in for faster compile/test cycle (self testable dynamic library)
* Protector to encapsulate test execution (allow capture of exception not derived from std::exception)
* MfcTestRunner
* QtTestRunner, a Qt based graphic test runner