ETF Quickstart


This project is only included on the OSGeoLive virtual machine disk (VMDK)

ETF is an open source testing framework for validating spatial data, metadata and web services in Spatial Data Infrastructures (SDIs). The design of ETF is driven by three goals: be user-friendly, consistent with the standards and capable of testing all resources in an SDI.

This Quickstart describes how to:

  • navigate through the web application

  • start a test

  • monitor a test run

  • watch and manage test reports


From the OSGeoLive Start menu, select Geospatial ‣ Spatial tools ‣ ETF. The application will take a few moments to start up and will open a web page at http://localhost:9090/ETF

In the header, there is a menu with 4 sections, each representing different views and functionalities:

  1. The first one is Start test. In this section all available (i.e. installed) Executable Test Suites are listed. Within this section, an Executable Test Suite can be selected and run against a Test Object.

  2. The second one is Status. This one shows all tests that are currently being executed on the system and allows to open a monitor view for single test runs to check the status of any running test. Moreover, the components currently loaded are shown below the running tests.

  3. The third one is Test reports. In this one the results of any completed test can be checked, analysed in detail or downloaded.

  4. The fourth one is Help. This one is a link to the documentation. Inside it, there are guides on how to use all functionalities of the ETF.

Start test

Test Suite Selection

The landing view shows the available Executable Test Suites.


Additional information about a Test Suite can be accessed by clicking on the + button.


This information:

  • Includes a description of the Test Suite.

  • May include a link to the Abstract Test Suite from which the Executable Test Suite has been derived (Source).

  • May include the Test Suite dependencies, which are automatically executed with the Test Suite in a Test Run (Pre-requisite conformance classes).

  • May include the name of associated Tags which are used to group the Test Suites in the view.

  • Includes the name of applicable Test Object Types (explained in the next section).

  • Includes general information like the version, author and last editor, creation and change dates.

To start a Test Run, a Test Suite must be selected with a click on the use flip switch on the right-hand side.


A Start button appears once at least one Test Suite is selected.

A Test Suite is only applicable to certain Test Object Types, which are listed in the description. Multiple Test Suites can be selected for one Test Run, but must be applicable to the same Test Object Type. Once one Test Suite is selected, the flip switch of all other Test Suites having different Test Object Types is disabled.


A Test Suite may depend on other Test Suites. The dependencies are also shown in the description of the Test Suites. These dependencies are also automatically executed during the test run.

A click on the Start button will open a new view that asks the user about the target resource to be tested.

Test Run configuration


The Label field is mandatory and automatically preset with the current time and names of the selected Test Suites. The Label will be shown in the Test reports section and can be changed in order to help find the report again after a test run.

The style of the view may depend on the selected Test Suites.

File-based Tests

The following elements are shown when Test Suites have been selected that test one or multiple test data files.

If File upload is selected as Data source, one or multiple local files can be selected and uploaded to the ETF. The ETF only accepts files with XML and GML file extensions as well as ZIP files containing these two file types.


Other files, like schema definition files, cannot be used and are silently ignored by the ETF!


The maximum uploadable file size is displayed when the mouse is moved over the question mark.

If the data to be tested are available on the web, they can be tested by providing one single URL. After Remote file (URL) has been selected as Data source, a Remote URL to either one single XML, GML or a ZIP file can be entered.


If the URL requires authentication, username and password can be provided by clicking on Credentials.


Service Tests

The following elements are shown when Test Suites have been selected that test one service.

The Service URL must be entered beginning with http:// or https://.


If the service requires authentication, username and password can be provided by clicking on Credentials.

Dependencies and Parameters

The Test Suites button shows some basic information about the selected Test Suites and - if applicable - about the direct dependencies.


If the Test accepts parameters, they are shown in the Test Suite Parameters section. Optional parameters can be displayed by clicking on the Optional Parameters button. A description of the parameters is displayed when the mouse is moved over the question mark.


In most cases the preset default values can be used.


Finally the test can be started by clicking on the Start button. The view then changes automatically to the Monitor Test Run view.

Monitor test runs

After a Test Run has been started the Monitor Test Run view is shown.


The blue bar indicates the progress.


The console area shows information and result messages. The Test Run can be canceled with a click on the Cancel button.

The view can be closed, for instance with the X Button in the upper left corner. Also when the browser is closed, the Test Run execution continues on the server.

To reopen the Monitor Test Run view after it has been closed, select in the menu bar the Status section. The Status section shows all running tests. A click on the Test Run opens the Monitor Test Run view of that Test Run.


When a Test Run finishes and the Monitor Test Run view is opened, the Test Report is displayed automatically.

Test Reports

The Test Reports section shows all reports that have been generated from Test Runs.


By clicking on the + button information for a Test Run, the start time, the test result status, the name of the Test Object and the used Test Suites are shown.

A Test Report can be opened again by clicking on the Open report button or can be downloaded as HTML file by clicking on the Download report button.

The log file of the test run can be inspected with the Open log button. By clicking on the Delete report button, the report will be deleted permanently.

Inspect test reports

The top of a Test Report shows general information including the overall test result status, the start time, the duration and a table, which summarizes the status of all tests on several levels.


The Test Reports are interactive. The Show switch can be used to filter Only failed or Only manual tests. The option All deactivates the filter.

The Level of detail switch is used to show more or less information in the reports.


The test results are summarized hierarchically in a report. At the top level there are the Test Suites.

By clicking on one Test Suite, a description and all lower level tests in that Test Suite are shown. Errors in a Test Suite can be immediately recognized by the red color. The number of failed tests is shown in the top-right corner.


The green color indicates a passed test. Passed tests, which require additional manual test steps that could not be automated, are colored orange. The orange color may also indicate a test that has been skipped because it depends on another test that has failed. The exact status can be found below the description.

The number of levels depends on the tested Test Object. If service tests have been executed, the hierarchy is as follows:

  • Executable Test Suites

  • Test Modules (bundles Test Cases)

  • Test Cases (bundles Test Steps)

  • Test Steps (interactions with the service, bundles Test Assertions)

  • Test Assertions (atomic tests)

In a file-based test, Test Modules and Test Steps do not exist and are not shown in the report.

Each test lists the requirements and provides a description on how they are tested. The test may include a link to an Abstract Test Suite, from which the test has been derived (Source).


Assertions stand for atomic test queries on the lowest level. Failed, red colored assertions display error messages in the Messages section.


Helpful information may also be found on the next higher level, like for instance the response from a service on the Test Step level (note the Open saved response link in the report).



Using the instructions provided above, please find below a predefined set of resources that you can test in the ETF:

  • GML data sets: some predefined data sets can be downloaded from here.

  • WMS services: a list of services is available here.

  • WFS services: a list of services is available here.


Some of the GML data sets provided above do not pass all the tests, so you can try to fix them (based on the errors reported in the test report) before validating them again until all tests succeed.

What’s next?

This was just a very brief overview of the ETF. There is more information in the demo installation and on the ETF GitHub space.

Please also check: