Terminology

• Unit

  An incomplete collection of modules, e.g. source files, object files and/or library files. When combined these modules form the unit that is tested. The instrumenter will fill in the missing pieces in order to form a complete test executable.

• Test executable

  The output of the instrumenter. The test executable will run the tests and report errors found.

• Test

  The test is the basic test implementation by the test designer. It is composed of one single C function, that will call the selected functions in the unit and validate the behavior.

• Testcase

  It is common to group several tests to form a more complete test - for example, software that implement some kind of state machine may require several tests to be executed, before a scenario is covered.

  It is a possibility for the test designer to form testcases by nesting tests.

• Testsuite

  It is a possibility for the test designer to form testsuites by nesting testcases.

• Stub

  A stub is a function that replaces non-existing functionality in the unit by providing an alternative test implementation for the function it replaces.

  The test developer can choose to implement a stub manually. Manually created stubs are not dynamic - they remain in scope for all tests at all times.

  If a stub is not created manually, the framework will automatically create a default TestApe mock.

• Mock

  A mock is a function the replaces or extends existing functionallity by providing an implementation for the function it mocks.

  The mock implementation is defined by the test developer. The mock will typically verify parameters and simulate a return value for the unit. In addition the mock function can choose to call the function it is mocking.

  Default mocks are automatically generated for those functions that are not part of the unit. TestApe mocks dynamic scope. Each test define which functions that are mocked and which mock implementation they use for each test.

• Instrumenter

  A tool provided in the package, that will create default mocks for those functions, that are not present in the unit.

• Framework

  The TestApe framework is a library wrapped in a collection of macros. The macros are used when writing test.