Conformance Test Suite - GML in JPEG 2000 2.0

Scope

This executable test suite (ETS) verifies the conformance of JPEG 2000 codestreams against OGC GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1 (OGC 08-085r4) and related specifications (see Figure 1). The JPEG 2000 standard (ISO 15444 series) is a wavelet-based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file. Conformance testing is a kind of "black box" testing that examines externally visible characteristics or behaviors of the IUT and is independent of any implementation details.

specifications
Figure 1. Relevant specifications

Several conformance classes are defined in the principal specifications; the ones listed below are covered by this test suite:

Test requirements

The documents listed below stipulate requirements that must be satisfied by a conforming implementation.

  • OGC 08-085r4: OGC GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core, Version 2.0

  • OGC 12-108 OGC GML Application Schema - Coverages - JPEG2000 Coverage Encoding Extension, Version 1.0

  • OGC 09-146r2: OGC GML Application Schema - Coverages, Version 1.0.1

  • ISO/IEC 15444-2:2004: Information technology — JPEG 2000 image coding system: Extensions

  • ISO/IEC 15444-1:2004: Information technology — JPEG 2000 image coding system: Core coding system

Test suite structure

The test suite definition file (testng.xml) is located in the root package, org.opengis.cite.gmljpx20. A conformance class corresponds to a <test> element, each of which includes a set of test classes that contain the actual test methods. The general structure of the test suite is shown in Table 1.

Table 1. Test suite structure
Conformance class Test classes

Core

  • org.opengis.cite.gmljpx20.core.*

The Javadoc documentation provides more detailed information about the test methods that constitute the suite.

How to run the tests

The options for running the test suite are summarized below.

1. Integrated development environment (IDE)

Use a Java IDE such as Eclipse, NetBeans, or IntelliJ. Clone the repository and build the project.

Set the main class to run: org.opengis.cite.gmljpx20.TestNGController

Arguments: The first argument must refer to an XML properties file containing the required test run arguments. If not specified, the default location at $ {user.home}/test-run-props.xml will be used.

You can modify the sample file in src/main/config/test-run-props.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties version="1.0">
  <comment>Test run arguments</comment>
  <entry key="iut">iut.jp2</entry>
</properties>

The TestNG results file (testng-results.xml) will be written to a subdirectory in ${user.home}/testng/ having a UUID value as its name.

2. Command shell (console)

One of the build artifacts is an "all-in-one" JAR file that includes the test suite and all of its dependencies; this makes it very easy to execute the test suite in a command shell:

java -jar ets-gmljpx20-${version}-aio.jar [-o|--outputDir $TMPDIR] [test-run-props.xml]

3. Docker

This test suite comes with a Dockerfile which can be used to easily setup the OGC test harness with the test suite. Details can be found on Create Docker Image and create and start Docker Container.

4. OGC test harness

Use TEAM Engine, the official OGC test harness. The latest test suite release are usually available at the beta testing facility. You can also build and deploy the test harness yourself and use a local installation.

Using the REST API

Using the REST API of the TEAM Engine requires some run arguments. These ate summarized in Table 2. The Obligation descriptor can have the following values: M (mandatory), O (optional), or C (conditional).

Table 2. Test run arguments
Name Value domain Obligation Description

iut

URI

M

A URI that refers to the test subject. Ampersand ('&') characters must be percent-encoded as '%26'.