TG MTS Test campaign – performing the Model ETS

From Wikicap - European Commission

Go up to the main TG MTS

The model test campaign is the process of executing the model ETS and recording the observed test outcome and relevant information in the conformance log. Both the input to the IUT and the observed test outcome for each test case shall be recorded in the conformance test log report file (MTS - ModelTesSuite.XML). This recording and retention of all information is necessary for the analysis phase and for auditing purposes (ISO/TC211 2000).

During this testing phase, both manual and automatic testing are possible and allowed. A feature catalogue will always require manual testing while computer based testing can be possible when an application schema is available in an appropriate machine readable presentation (for example XML). DG JRC does not provide computer software for such automatic MTS tests.

Elements that are related to the environment in which the implementation shall be tested and considered important can still be collected as “Extra Information for Testing (IXIT}. In particular, this additional information should provide the details on organization and storage in the system and on the means of access. If needed, conversion methods between the concepts of the tested LPIS implementation and the LCM have to be developed.

The testing phase involves the following loop:

  • Retrieve the executable test case from the predefined (by DG JRC) list which is stored in application schema (ModelTestSuite.XSD) Table 1.
  • Review whether the case has to be complemented with parameters. An executive test may be supplemented according to the specificities of the MS SUT. Where and when appropriate, document the resulting executive test case on test purpose, test method and other characteristics.
  • Run the (modified) executable test case against your SUT. Each test call can be executed either manually, or automatically (with or without dedicated testing software) Figure 3.
  • Document all informative messages in the test log file.

All 47 executable test cases should be conducted. A verdict should be given (assigned) to each of them.


Figure 3: MTS item inspection

After all model executive test cases have been performed, the criteria and testing outcomes should be described in the (conformance) test log report file (ModelTesSuite.XML). The test log report should also hold the executable test case descriptions as informative messages for those that are defined/modified by the MS. Examples of each test are described in different documentation parts of application schema (ModelTesSuite.XSD) and the example case of Figure 4.

Go up to the main TG MTS page