Skip to content

Testplan

Jump to bottom
tfr42 edited this page Jun 13, 2025 · 3 revisions

Test Plan deegree ogcapi (version 1.3.5)

Test Case-01: /deegree-ogcapi/datasets/

Step Description Expected Result
01 The user clicks on the JSON button in the top right corner of the HTML page. A new tab showing the information in the JSON view opens.
02 The user clicks on the Help button in the bottom left corner of the HTML page. A new tab opens up with helping instructions.
03 The user clicks on the Legal Notice button in the bottom right corner of the HTML page. A new tab opens up, showing the contact of the distributor and all Legal Notice requirements.
04 The user clicks on the Privacy Policy button in the bottom right corner of the HTML page. A new tab opens up, showing all the Privacy Policy requirements.
05 The user clicks the link under the Contact Title. A new website opens up, with the contact information of the distributor.
06 The user clicks on any of the listed links with Landing Page as HTML. The user jumps to the collections of the dataset under /deegree-ogcapi/datasets/dataset.

Test Case-02: /deegree-ogcapi/datasets/dataset

  • Step 06 from Test Case-01 has been successfully completed.

Preconditions

Step Description Expected Result
01 The user clicks on the JSON button in the top right corner of the HTML page. A new tab showing the information in the JSON view opens.
02 The user clicks on the XML button in the top right corner of the HTML page. A new tab showing the information in the XML view opens.
03 The user clicks on a corresponding link of the listed title API Definition. The API definition opens in the HTML view.
04 The user clicks on a corresponding link of the listed title Conformance Classes. The OGC API conformance classes open in the HTML view.
05 The user clicks on a corresponding link of the listed title Metadata. The metadata, describing the dataset open.
06 The user clicks on a corresponding link of the listed title Contact. The page or the email of the contact regarding the dataset opens.
07 The user clicks on a corresponding link of the listed title License. The license of the dataset opens.
08 The user clicks on a corresponding link of the listed title Collections. The user jumps to the collections of the dataset under /deegree-ogcapi/datasets/dataset/collections.

Test Case-03: /deegree-ogcapi/datasets/dataset/collections

Preconditions

  • Step 08 from Test Case-02 has been successfully completed.
Step Description Expected Result
01 The user clicks on the JSON button in the top right corner of the HTML page. A new tab showing the information in the JSON view opens.
02 The user clicks on the XML button in the top right corner of the HTML page. A new tab showing the information in the XML view opens.
04 The user clicks the link Features as HTML. A new tab opens listing all the Features in a HTML view.
05 The user clicks the link Download all features as GeoJSON. All features are downloaded as a JSON file.
06 The user clicks the link Download all features as GML. All features are downloaded as a GML file.
07 The user looks for the supported Coordinate Reference Systems. The corresponding Coordinate Reference Systems of the collections are listed.
08 The user looks for the Item type. The given Item type is listed.
09 The user clicks on the link Collection as HTML. The user jumps to the collections of the dataset under /deegree-ogcapi/datasets/dataset/collections/collection.

Test Case-04: /deegree-ogcapi/datasets/dataset/collections/collection

Preconditions

  • Step 09 from Test Case-03 has been successfully completed.
Step Description Expected Result
01 The user clicks on the JSON button in the top right corner of the HTML page. A new tab showing the information in the JSON view opens.
02 The user clicks on the XML button in the top right corner of the HTML page. A new tab showing the information in the XML view opens.
04 The user clicks the link Download all features as GeoJSON. All features are downloaded as a JSON file.
05 The user clicks the link Download all features as GML. All features are downloaded as a GML file.
06 The user sees the Spatial Extent as a Bounding Box in the interactive Map and interacts with it. The user can interact with the Bounding Box of the interactive Map by zooming in and out.
07 The user looks for the supported Temporal Extent. The corresponding Temporal Extent of the chosen collection are listed.
08 The user looks for the supported Coordinate Reference Systems. The corresponding Coordinate Reference Systems of the chosen collection are listed.
09 The user looks for the Item type. The given Item type is listed.
10 The user clicks on the link Features as HTML. The user jumps to the items of the dataset under /deegree-ogapi/datasets/dataset/collections/collection/items.

Test Case-05: /deegree-ogcapi/datasets/dataset/collections/collection/items

Preconditions

  • Step 10 from Test Case-03 has been successfully completed.
Step Description Expected Result
01 The user clicks on the GeoJSON button in the top right corner of the HTML page. A new tab showing all the listed items/features in the JSON view open.
02 The user clicks on the GML button in the top right corner of the HTML page. All listed items are downloaded as a GML file.
03 The user browses the interactive Map through Mouseover. The geometries on the map reveal their specific Feature-ID.
04 The user looks up if all the listed Feature-IDs are available as geometries on the interactive Map. All the listed Feature-IDs are visible as geometries on the interactive Map.
05 The user looks if the listed Feature-IDs and the displayed geometries are coherent. The listed Feature-IDs and the geometries match up.
06 The user clicks on a any given Feature-ID. The user jumps to the selected item/feature under /deegree-ogcapi/datasets/dataset/collections/collection/Items/itemname.

Test Case-06: /deegree-ogcapi/datasets/dataset/collections/collection/items/itemname

Preconditions

  • Step 06 from Test Case-05 has been successfully completed.
Step Description Expected Result
01 The user clicks on the GeoJSON button in the top right corner of the HTML page. A new tab showing the listed item/feature in the JSON view opens.
02 The user clicks on the GML button in the top right corner of the HTML page. The listed item/feature are downloaded as a GML file.
03 The user clicks on the a specific Feature-ID. A new tab opens up listing an expanded attribute table and the specific location of the item/feature on the interactive Map.
04 The user scrolls down the attribute table and clicks the link Collection as HTML. The user jumps back to the collection of the dataset under /deegree-ogcapi/datasets/dataset/collections/collection.

Test Case-07: /deegree-ogcapi/datasets/dataset/collections/collection/items/query-parameters

Preconditions

  • Test Case 01-06 has been successfully completed.
  • A running deegree-ogcapi instance using the strassenbaumkataster dataset.
Step Description Expected Result
01 To specify the desired response format, the user uses the f query parameter. For example using f=xml: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items/APP_STRASSENBAUMKATASTER_100055201?f=xml. A download for a GML file is triggered that contains the in the request specified item.
02 To paginate items, the user uses the offset parameter to skip a number of entries. For example using offset=100: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?offset=100. The HTML view shows items starting from the 101st item of the dataset, as the offset=100 parameter skips the first 100 items.
03 To limit the number of returned items, the user uses the limit parameter. For example using limit=30: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?limit=30. The HTML view shows the first 30 items of the dataset on the first page, as specified by the limit=30 parameter.
04 To request the items in a specific coordinate reference system (CRS), the user uses the crs parameter. For example using crs=EPSG:25832: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?f=json&crs=EPSG:25832. The JSON view shows the first 10 items of the dataset with the coordinates transformed to EPSG:25832 (i.e.: 567197.5176, 5934342.7515).
04.1 The crs parameter can also be used with the OGC URI notation. For example using crs=http://www.opengis.net/def/crs/EPSG/0/25832: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?f=json&crs=http://www.opengis.net/def/crs/EPSG/0/25832. The JSON view shows the first 10 items of the dataset with the coordinates transformed to EPSG:25832 (i.e.: 567197.5176, 5934342.7515).
05 To request items in a specific area, the user uses the bbox parameter. The The BBOX CRS is determined by the bbox-crs parameter. For example: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?bbox=567190,5934330,567200,5934360&bbox-crs=EPSG:25832. The HTML view shows the items that are inside the defined BBOX, as specified by the coordinates of bbox=567190,5934330,567200,5934360.
06 To request a bulk download of items in the XML format, the user uses the bulk=true parameter in combination with f=xml. For example: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?f=xml&bulk=true. A download is triggered that includes the items specified in the request with the parameters f=xml in combination with bulk=true.
07 To request items filtered by dates after a specific point in time, the user uses the T_AFTER parameter. For example using T_AFTER(pflanzjahr,DATE('2016-12-30')): /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?filter=T_AFTER(pflanzjahr,DATE('2016-12-31')). The HTML view shows the items that have a pflanzjahr later than 2016-12-31, according to the applied T_AFTER filter.
07.1 To request items filtered by dates after a specific point in time, the user uses the T_AFTER parameter. For example using T_AFTER(pflanzjahr,DATE('2017-01-01')): /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?filter=T_AFTER(pflanzjahr,DATE('2017-01-01')). The HTML view shows no items, because there are no features with a pflanzjahr later than 2017-01-01, as specified by the T_AFTER filter.
08 To request items filtered by spatial intersection, the user uses the S_INTERSECTS parameter with a polygon geometry. The filter-lang=cql2-text parameter defines the filter language, and filter-crs=EPSG:25832 specifies the coordinate reference system of the geometry used in the filter. For example: /deegree-ogcapi/datasets/strassenbaumkataster/collections/strassenbaumkataster/items?f=json&crs=EPSG:25832&filter-lang=cql2-text&filter=S_INTERSECTS(geometry,POLYGON((564000 5917000,564000 5950000,602000 5950000,602000 5917000,564000 5917000)))&filter-crs=EPSG:25832. The HTML view shows the items whose geometry intersects the specified polygon area, according to the S_INTERSECTS spatial filter, interpreted in the EPSG:25832 coordinate system.

Clone this wiki locally