SelfTest Namespace Reference

The SelfTest plug-in provides a basic unit test framework that can be used by other plug-ins to implement self-testing. More...

Classes
class	SelfTestPlugin
class	Test
	The Test template class is used to define a new test. More...
class	TestBase
	The Test class is the base class for a single test for the Envision testing framework. More...
class	TestManager
	The TestManager class manages test registrations and execution for each plug-in. More...
class	TestResult
	The TestResult class describes the outcome of a single test or check. More...
class	TestResults
	The TestResults class describes the outcome of series of tests run consecutively. More...

Detailed Description

The SelfTest plug-in provides a basic unit test framework that can be used by other plug-ins to implement self-testing.

Plug-in developers are encouraged to write code that tests their implementations using the services of SelfTest, but it is also possible to use other testing approaches.

Clients who want to implement tests can do so with minimal efforts by using convenience macros defined within SelfTest. All tests for a plug-in are automatically registered with a TestManager. It can be used to run all tests or a specified test and report statistics. SelfTest offers a collection of commonly used assertions and checks and provides exception handling support. Classes for test cases are only allocated on request and do not occupy memory if tests are not running.

Running a test from the command line

Indicating that a specific plug-in should be tested after Envision is initialized can be done using the –test switch on the command line. Here is the syntax for this command:

envision --test pluginid[:testid] [pluginid:[testid]] ... 

pluginid is a mandatory argument that specifies which plug-in needs to be tested.

If testid is specified only the corresponding test will be run, otherwise all tests for the indicated plug-in will be executed.

To test multiple plug-ins or to run multiple tests for a plug-in, specify additional pluginid:testid pairs. Here are some examples:

envision --test modelbase 

Runs all tests for the modelbase plug-in.

envision --test modelbase:RemoveOptional 

Runs only the RemoveOptional test for the modelbase plug-in.

envision --test modelbase:RemoveOptional modelbase:ListCreation oomodel 

Runs the RemoveOptional and ListCreation tests for the modelbase plug-in and all tests for the oomodel plug-in. The tests will be run in the order indicated on the command line.