Creating Test Suites for Unit Test Pro

Creating a test suite is very easy. A test suite is simply a DLL that contains your test functions. The test suite code is object-oriented C++, and can be easily created by copying the SampleUnitTest project included with Unit Test Pro. Note that you can do anything in your test suite DLL that you can do with any other C++ module.

To create a test suite you will:

• Create a DLL project to contain your test code. You can use the SampleUnitTest project provided in the Unit Test Pro installation folder. Simply copy the project files and modify to suit your needs.
  
• Include the UnitTestCase.h header in your code module.
  
• Create a class derived from the CUnitTestCaseSuite class.
  
• Override the ConstructTestSuite function to define the name of the test suite and to define the test functions.
  
• Optionally override the SetupTestSuite and TearDownTestSuite functions to set up the test environment before tests are executed, and tear it down after test execution has completed. You can use these functions to prepare your test environment and then clean up the test environment when the tests run has completed. These functions can do such tasks as starting or stopping services, establishing database connections, setting up test files, etc.
  
• Include the construction and destruction macros which provide the hook for Unit Test Pro to create and destroy your test case suite.
  
• Write your tests. You will need to include all code you require to run your tests, and you need to write the test functions themselves.
  

The easiest way to create a new test suite DLL is to simply copy the SampleUnitTest project and modify it to contain your test code. Once you have created a test suite to operate on your code, from that point on it is an easy task of simply copying an existing test suite DLL you have created in order to create a new test suite.  

Unit test suites can contain any number of test functions and can perform any operations that a standard C/C++ module can. Generally, test suites contain related tests and you create a separate test suite for each of your groups of related tests.