Loading...
 
ESA > Join & Share > HMA-T > HMA-T ATS guidance Infoterra
Print

HMA-T ATS guidance Infoterra

Guidance on defining an Abstract Test Suite (ATS) for EO Application Profiles of OGC specifications


These notes give basic guidance on defining an Abstract Test Suite for EO profiles of OGC Web services and should be read with reference to the ~~#3300CC:WMS_EO Profile Abstract Test Suite (ATS)~~ example which may also be used as a template. The WMS EO Profile ATS is itself based on the WCS 1.1 ATS. For metadata specification profiles (which do not define Web service behaviour), reference can be made to the KML 2.2 ATS document.

An Abstract Test Suite is described in a conformance clause where Abstract Test Cases (ATCs), formal basis for deriving executable test cases, are grouped in abstract test modules in a hierarchical structure.

Profiles of OGC specifications may be of two types:

  • type 1 profiles that provide with a specific interpretation or sub-set of the metadata structures and/or behaviour of an OGC specification;
  • type 2 profiles than, in addition, define extensions to the metadata and/or behaviour of an OGC specification.


In either case, the related Abstract Test Suite should not attempt to redefine the baseline OGC specification but should set out the ATCs for the features that constrained and/or extended the baseline specification.

The overview section of the ATS should define the structure of the document, setting out the hierarchy of abstract test modules. For a Web service profile, this grouping should follow the operations affected (e.g. GetCapabilities, GetMap, GetFeature, etc.). Conformance levels (level 1 for mandatory, level 2 for optional) should be used where relevant.

Each ATC within an abstract test module should be laid out as a table with the 5 rows defining:

  1. test-case identifier;
  2. test purpose(s);
  3. test method (including test-verdict criteria);
  4. reference to specific standard(s);
  5. test types (either a basic test or a capability test).


The test purpose is a brief, general description of the reason for the test. The test method lists (via a sub-table) the parameters and operations needed for the Web service request(s) that test a specific behaviour. More complex test methods, that include more than one request, may need to define:

  1. an initial request case (such as GetCapabilities);
  2. extraction of parameters in the response to the initial request case;
  3. definition of the service type, request operation and necessary parameters for a secondary request.


The test method also defines the pass criteria for the test which are based on the response to the Web service request.


Contributors to this page: Thomas Lankester .

Page last modified on Monday 20 of October 2008 17:17:17 CEST by Thomas Lankester.

Category: HMA-T