TG MTS Model ATS - Abstract Test Suite

From Wikicap - European Commission

Go up to the main TG MTS

A model ETS is produced as a result of selecting abstract test cases and assigning parameter values based on the model ATS. At this point, the IUT and the scope of the conformance assessment process are fixed and cannot be changed subsequently.

The scope of this TG MTS covers 3 abstract test cases (model ATS) upon which initial executable test cases (model ETS) are proposed. These abstract test cases are strictly within the LCM scope. They are design based on the assumption that the IUT and the correspondent SUT are well documented (feature catalogue, conceptual model, system implementation and architecture, database structure, etc.). Separate “system definition” tests, dedicated to check the availability of the relevant documentation and retrieve information about the MS’s system (unrelated to LCM), are not required for this version of the MTS (v2.0).

The naming of the 3 abstract test cases is quite self-explanatory on their intended purpose:

  • featureTypeCompletness – check for availability all required features types
  • attributeTypeCompleteness – check for the availability of all require attributes for a given feature type
  • extendedCodeList – check for availability of a complete list of values in the required code list

A set of 47 initial executable test cases has been proposed to test model properties regarding 4 LCM entities. For the purpose of the data testing of the annual quality assessment, only these four entities are relevant.

  • ReferenceParcel
  • AgriculturalLand, including the NonAgriEligibleLand
  • LandscapeFeature
  • Anomaly

A test log report template (ModelTestSuite.XML) is derived from a regular, standard application schema (ModelTestSuite.XSD), using an UML class diagram (Figure 2).

ModelTestSuite v 2 2.png


Figure 2: Application schema ModelTesSuite.XSD

These 47 executable test cases derived from the 3 abstract test cases have been prepared by DG JRC without providing a hierarchy of the tests. The specific hierarchy depends on the SUT implementation options. Although initial descriptions for each executable test case have been prepared by DG JRC, some of these descriptions can be considered as indicative. MS can adapt them depending on their system. The resulting hierarchy, IUT, identifiers, descriptions of methods and purposes together with the applicable parameters should be extensively documented by MS.

In addition to the diagram in Figure 2, all 3 abstract and all 47 executable test cases are provided in Table 1 below. The names of columns are derived from application schema (ModelTesSuite.XSD) directly. The exact element description can be retrieved by the online http://lpis.jrc.ec.europa.eu/CAP_IACS/index.htm (European Commission DG JRC 2015); simply remove the string “check” from the mnemonic name of executable test case name below (Executable Test Case Name column).

E.g. For the executable test case name “checkreferenceArea” the corresponding element in LCM online will be “referenceArea”. All descriptions of each element then can be found by navigating within it in LCM.

In Table 1 there is no column “Executable test method”. This is on purpose as to avoid redundancy in the table, as it implied by the column “executable test type”. There is only one method for all executable test cases within TG MTS which is the capability test.

This capability test performs a source (LCM) to target (SUT) element mapping, identifies the model element in the SUT that corresponds to the specified LCM element. If a correspondence is found or if there is a documented evidence that for the given IUT this element is not applicable (case of landscape features), the test will pass and the names of corresponding element(s) or evidences shall be documented in the test result.

The feature elements expected to be present in any IUT, are the Reference parcel, the Agriculture Land (including the Non Agricultural Eligible Land), Aid Application, and Anomaly. If any of these elements is absent in the SUT, the test will fail. The presence feature elements Landscape Feature is optional, depending on the choices made by the EU Member State.


Table 1: The list of abstract and executable test cases. Each test case has its purpose, type and example of result description (in case test verdict – “Pass”).

Table1-1 new.jpg Table1-2 new.jpg Table1-3 new.jpg Table1-4 new.jpg Table1-5 new.jpg Table1-6 new.jpg


Go up to the main TG MTS page