Skip to content

opengeospatial/ets-geotiff11

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GeoTiff 1.1 Test-Suite

Scope

The GeoTiff 1.1 Test-Suite is an Executable Test Suite (ETS) that verifies implementations against the GeoTiff 1.1 (and 1.0) specifications.

See specification documentation here.

Two conformance classes are defined:

Bugs

Issue tracker is available at github.

How to run the tests

The test suite is built using Apache Maven v3. The options for running the suite are summarized below.

Dependency requirement

On Linux, the test suite requires libtiff-tools.

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.geotiff11.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">[GEOTIFF HERE].tiff</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 target/ets-geotiff11-0.1-SNAPSHOT-ctl.jar [-o|--outputDir $TMPDIR] [xml-file]

Where xml-file is the path to the properties XML file, e.g., src/main/config/test-run-props.xml.

3. 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.