Getting Started
Installation
The TEFUnit is installed automatically by the SITK installer during the
installation of TestDriver. For further information on how to install the SITK
refer to System Integration Toolkit Guide >> Introduction to the
System Integration Toolkit >> Installation and setup.
Quick start guide
This quick start guide is intended to show the minimum steps necessary
to create test input files, execute tests and analyse test results. Minimal or
no explanation is provided for each step and you must refer to the relevant
sections for more comprehensive information.
-
Create test input files: Developing unit tests
consists of creating a derived test fixture class with a list of test cases,
and providing the framework with some hierarchy information and a test server
name. It also includes configuring the .ini
file and the script
file.
-
Implement a C++ class: The unit tests need to be
included in a CTestFixture
derived class and each test case needs
to be added to a suite for that fixture. You must write a
CreateSuiteL()
function to provide the TEFUnit framework with the
suite hierarchy information.
-
Define the Global Functions: You must define the
Test Suite Hierarchy, TEF Step Hierarchy and provide a name for the TEF server.
-
Create configuration information files: The
configuration data or input values used for testing are provided using a
.ini
file.
-
Develop script file: A text file, with a
.script
extension, containing a series of commands is used for
performing test execution.
-
Execute the test: Execute the tests by invoking
testexecute.exe
from the eshell prompt and provide the script-file
path as a command line argument along with any run-time options.
-
Analyse the test results: The results are in the form
of HTML or XML log files with the same name as that of the script file. They
are placed by default under c:\logs\testexecute
.
Using the documentation
For information on how to use TEFUnit documentation, refer to
System Integration Toolkit Guide >> Introduction to the System
Integration Toolkit >> Using the documentation.