In STIF, test cases are collected into separate modules, called test modules, which contain the actual test case implementation.
There can be several test cases implemented in one test module, and test cases can be defined, for example, by a test case file (a configuration file). In addition, STIF supports running different test cases simultaneously from several test modules.
The following test module types are available. Based on these types, the STIF Carbide.c++ Extension provides templates that simplify the test module creation:
Test module types | Description | Supported by TestDrop |
Normal | Creates an empty test module, where test cases can be freely implemented. This template type enables you to implement unique type of test cases or use old cases as basis for new ones. |
Yes |
Hardcoded | Creates a test module template where every test case is implemented as a separate function. |
Yes |
Testclass | Creates a test class for Test Scripter usage. |
Yes |
Kerneltest (for Test Scripter) | Creates a kernel test class for Test Scripter usage. |
No |
Capsmodifier | Creates a capability modification module for your test module. |
No |
STIFUnit | Creates test cases in the quickest possible way. STIFUnit limits the minimum number of files that need modification while adding a new test case. It also groups code common for all test cases, such as variables, their initialization and destruction. |
Yes |