Note that the definitions below may not be strict. It is quite difficult to provide strict and yet clear definitions for some of the terms described here.
"Shallow"-quality testsThese are usually simple tests with the only guaranteed purpose: to check that the interface does not crash being called with some set of correct parameters and in the correct environment. Additionally it can be checked that the interface does not return an error code. |
"Normal"-quality testsThese tests check the main functionality of an interface and may check a few error scenarios. |
"Deep"-quality testsDeep tests check the most of the specification assertions in various conditions/states. |
Elementary requirement (elementary assertion)Elementary requirement is a requirement (assertion) that cannot be split into smaller requirements or it is not reasonable to do so.
Here we only consider the requirements concerning the behaviour of the interfaces to be tested. That is, |
Test purpose, TPFrom TETware User Guide: A test purpose typically tests an individual element of system operation for conformance to some statement of required behaviour, and yields a result indicating whether or not the element passed the test. As far as T2C is concerned, Test purpose = {code from the <CODE> section} + {a set of parameters from the <PURPOSE> section} A test purpose corresponds to a function in the generated C file ("test purpose function"). Each test purpose function in a particular C file has a unique number that is shown in the name of the function, e.g. "test_purpose_4", "test_purpose_55", etc. Ideally, the test purposes should be independent on one another. In T2C each test purpose function is executed in a separate process and has its own copy of global data. A test case consists of one or more test purposes that check a common set of requirements (assertions) for the same interface(s). Each <BLOCK> section in a T2C file corresponds to a test case. From TETware User Guide: A test suite is the largest grouping of tests that can be processed by the TETware Test Case Controller. A test suite is made up of one or more test cases. A test case is the smallest test program unit that can be built or cleaned up by the Test Case Controller. A test case consists of one or more invocable components. An invocable component is the smallest test program unit that can be executed by the Test Case Controller. In our case each invocable component contains a single test purpose. |