TG MTS Conformance testing methodology
Go up to the main TG MTS
An abstract test suite (ATS) has a hierarchical structure consisting of abstract test cases that may be arranged in abstract test modules. An executable test suite (ETS) is an instantiation (=operational case) of an ATS, after specific values to all implementation-dependent parameters have been assigned. Each executable test case (within an ETS) is derived from an abstract test case (within its ATS) and so formulated that it can be run on the IUT. Examples are provided in “Example of result analysis” chapter of this document.
In the LPIS QA framework such ATS-ETS interaction is theoretically applied twice
- For the model test suite (subject of this document TG MTS), where the common model ATS may need to be instantiated by each LPIS implementation into an individual “model ETS”.
- For the data test suite, where the data ATS was not published but a common data ETS was directly published under the name TG ETS.
To ensure continuity with the past documentation, the short name “ETS”, whenever unspecified, always refers to the common “data ETS” described in TG ETS.
The (conformance) assessment process involves four phases as shown in Figure 1 (ISO/TC211 2000):
- preparation for testing;
- testing campaign;
- analysis of results;
- (conformance) test report.
All phases of the testing campaign that constitute the model-based testing (MBT), and are compiled within the given Model Test Suite (MTS), are addressed in this document.
Figure 1: Conformance assessment process overview (ISO/TC211 2000)
Go up to the main TG MTS page