The T2C ("Template-to-C") framework is designed for development of the "normal"-quality tests that can be used with the TETware Lite test harness.
Automatic generation of test purpose functions for each parameter set based on a test template ("a document with holes"). The generated C code is structured. It is clear, which interfaces are tested in a particular test purpose and which values of the parameters are used in this test purpose.
Requirement checks are linked to the specific places in the documentation. Requirement text (perhaps reformulated to improve readability) is output to the TET journal in case of failure. So during analysis of the TET journal it is easier to figure out what happened. Coverage analysis is also easier. (Each requirement has a unique ID which is output to the journal when the requirement is checked.)
Automatic generation of common TET support code: defining TET structures (e.g. tet_testlist) in a consistent way, etc.
Requirement (assertion) checks via special macros and functions, more convenient than using bare TET API.
Each test (test purpose) is executed in a separate process and thus it generally has far less effect on the other tests.
Maximum execution time can be specified. This can be useful if some tests may hang. (If they do, at least other tests will have a chance to be executed.)
Both global and per-test resource cleanup support.
Support for building a test executable that does not depend on TET features at all (no change in the code of the test required). This can be useful, for example, to debug the test or to obtain more data about the behaviour of the tested interfaces in case of failure.