Home >> test_engine >> wfs >> 1.0.0 >> wfs_assertions

Test Requirements and Assertions for WFS 1.0.0

ISSUE : 1.0.0

Copyright © 1999-2002 The Open Group Ltd. All Rights Reserved.


Preface

This document contains the assertertions for testing servers implementing the Web Feature Service 1.0.0 specification. This release includes the GetCapabilities and DescribeFeatureType tests.

For each assertion in the specifications, a corresponding entry in this test specification contains the following elements:

ID: The name by which the test is known
Class: An assertion Class as defined in IEEE Std 1003.3. These types are:
A A mandatory, testable assertion.
B A mandatory, but untestable assertion.
C An optional, testable assertion.
D An optional, but untestable assertion.
Scope: If an assertion is type C or D, this entry describes the option that needs to be supported in order to activate the test.
Text: The text of the assertion and a reference to the source specification from which the assertion is derived.
Note: Any supplementary information associated with the assertion. For example it may suggest a strategy for the test implementation of the assertion or it may propose rationale as to why a test is classified as untestable.

This specification uses the following conventions for convenience:

  • Element and attribute names are in UPPERCASE.
  • References to DTD entities are prefixed with percent sign (e.g. %PCDATA).
  • Literal text is enclosed in quotation marks.

Table of Contents

   basic - WFS Basic Tests
      basicGetCapabilities - GetCapabilities Tests
         getCapabilitiesGet - GetCapabilities over HTTP GET Tests
         getCapabilitiesPost - GetCapabilities over HTTP POST Tests

      describeFeatureType - DescribeFeatureType Tests
         describeFeatureTypeGet - DescribeFeatureType over HTTP GET Tests
         describeFeatureTypePost - DescribeFeatureType over HTTP POST Tests

      basicGetFeature - GetFeature tests
         basicGetFeatureGet - GetFeature tests (GET)
         basicGetFeaturePost - GetFeature tests (POST)
         basicGetFeatureComplex - GetFeature with complex values tests
            basicGetFeatureComplexGet - GetFeature with complex values tests (GET)
            basicGetFeatureComplexPost - GetFeature with complex values tests (POST)

         basicGetFeatureFilter - GetFeature filter tests
            basicGetFeatureFilterArithmetic - GetFeature arithmetic operators tests
               basicGetFeatureFilterArithmeticGet - GetFeature arithmetic operators tests (GET)
               basicGetFeatureFilterArithmeticPost - GetFeature arithmetic operators tests (POST)

            basicGetFeatureFilterComparison - GetFeature comparison operators tests
               basicGetFeatureFilterComparisonGet - GetFeature comparison operators tests (GET)
               basicGetFeatureFilterComparisonPost - GetFeature comparison operators tests (POST)

            basicGetFeatureFilterLogical - GetFeature logical operators tests
               basicGetFeatureFilterLogicalGet - GetFeature logical operators tests (GET)
               basicGetFeatureFilterLogicalPost - GetFeature logical operators tests (POST)

            basicGetFeatureFilterSpatial - GetFeature spatial operators tests
               basicGetFeatureFilterBBOX - GetFeature bbox operator tests
                  basicGetFeatureFilterBBOXGet - GetFeature bbox operator tests (GET)
                  basicGetFeatureFilterBBOXPost - GetFeature bbox operator tests (POST)

               basicGetFeatureFilterBeyond - GetFeature beyond operator tests
                  basicGetFeatureFilterBeyondGet - GetFeature beyond operator tests (GET)
                  basicGetFeatureFilterBeyondPost - GetFeature beyond operator tests (POST)

               basicGetFeatureFilterContains - GetFeature contains operator tests
                  basicGetFeatureFilterContainsGet - GetFeature contains operator tests (GET)
                  basicGetFeatureFilterContainsPost - GetFeature contains operator tests (POST)

               basicGetFeatureFilterCrosses - GetFeature crosses operator tests
                  basicGetFeatureFilterCrossesGet - GetFeature crosses operator tests (GET)
                  basicGetFeatureFilterCrossesPost - GetFeature crosses operator tests (POST)

               basicGetFeatureFilterDisjoint - GetFeature disjoint operator tests
                  basicGetFeatureFilterDisjointGet - GetFeature disjoint operator tests (GET)
                  basicGetFeatureFilterDisjointPost - GetFeature disjoint operator tests (POST)

               basicGetFeatureFilterDWithin - GetFeature dwithin operator tests
                  basicGetFeatureFilterDWithinGet - GetFeature dwithin operator tests (GET)
                  basicGetFeatureFilterDWithinPost - GetFeature dwithin operator tests (POST)

               basicGetFeatureFilterEquals - GetFeature equals operator tests
                  basicGetFeatureFilterEqualsGet - GetFeature equals operator tests (GET)
                  basicGetFeatureFilterEqualsPost - GetFeature equals operator tests (POST)

               basicGetFeatureFilterIntersects - GetFeature Intersect operator tests
                  basicGetFeatureFilterIntersectsGet - GetFeature Intersect operator tests (GET)
                  basicGetFeatureFilterIntersectsPost - GetFeature Intersect operator tests (POST)

               basicGetFeatureFilterOverlaps - GetFeature overlaps operator tests
                  basicGetFeatureFilterOverlapsGet - GetFeature overlaps operator tests (GET)
                  basicGetFeatureFilterOverlapsPost - GetFeature overlaps operator tests (POST)

               basicGetFeatureFilterTouches - GetFeature touches operator tests
                  basicGetFeatureFilterTouchesGet - GetFeature touches operator tests (GET)
                  basicGetFeatureFilterTouchesPost - GetFeature touches operator tests (POST)

               basicGetFeatureFilterWithin - GetFeature within operator tests
                  basicGetFeatureFilterWithinGet - GetFeature within operator tests (GET)
                  basicGetFeatureFilterWithinPost - GetFeature within operator tests (POST)






   transactional - Transactional WFS Tests
      transactionalGetCapabilities - Transactional GetCapabilities Tests
         transactionalGetCapabilitiesGet - Transactional GetCapabilities over HTTP GET Tests
         transactionalGetCapabilitiesPost - Transactional GetCapabilities over HTTP POST Tests

      transactionalInsert - Insert transaction tests over HTTP POST
      transactionalUpdate - Update transaction tests over HTTP POST
      transactionalDelete - Delete transaction tests over HTTP POST


   lock - Locking WFS Tests
      lockGetCapabilities - Lock GetCapabilities Tests
         lockGetCapabilitiesGet - Lock GetCapabilities over HTTP GET Tests
         lockGetCapabilitiesPost - Lock GetCapabilities over HTTP POST Tests

      lockLockFeature - LockFeature tests
         lockLockFeatureBasicTransactions - basic transaction LockFeature tests
         lockLockFeatureLockAction - lock action LockFeature tests
         lockLockFeatureLockExpiry - lock expiry LockFeature tests
         lockLockFeatureReleaseAction - release action LockFeature tests

      lockGetFeatureWithLock - GetFeatureWithLock tests
         lockGetFeatureWithLockBasicTransactions - basic transaction GetFeatureWithLock tests
         lockGetFeatureWithLockLockExpiry - lock expiry GetFeatureWithLock tests
         lockGetFeatureWithLockReleaseAction - release action GetFeatureWithLock tests



basic - WFS Basic Tests

There are no testable assertions in this section.

basicGetCapabilities - GetCapabilities Tests

There are no testable assertions in this section.

getCapabilitiesGet - GetCapabilities over HTTP GET Tests

ID: wfs/1.0.0/basic/getcapabilities/get/1
Class: A
Text: When a wfs:GetCapabilities request is made for a version number that the server supports, the result document must be a wfs:WFS_Capabilities with the version number equal to the version number in the request. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will define the version number to be 1.0.0. The response document will be tested to check that the version number returned in the capabilities document is the same as the requested version.

ID: wfs/1.0.0/basic/getcapabilities/get/2
Class: A
Text: When a wfs:GetCapabilities request is made for a version number that is greater than the version the server supports, the result document must be a wfs:WFS_Capabilities with the version number equal to the highest version number that the server supports which is less than the requested version number. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will define the version number to be 99.99.99. The response document will be tested to check that the version number returned in the capabilities document is less than 99.99.99.

ID: wfs/1.0.0/basic/getcapabilities/get/3
Class: A
Text: When a wfs:GetCapabilities request is made for a version number that is less than the version the server supports, the result document must be a wfs:WFS_Capabilities with the version number equal to the lowest version number that the server supports which is greater than the requested version number. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will define the version number to be 0.0.0 The response document will be tested to check that the version number returned in the capabilities document is greater than 0.0.0.

ID: wfs/1.0.0/basic/getcapabilities/get/4
Class: A
Text: When a wfs:GetCapabilities request is made without specifying a version number, the result document must be a wfs:WFS_Capabilities with the version number equal to the highest version number that it supports. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will noy define a version number. The response document will be tested to check that the version number returned in the capabilities document is greater than 0.0.0 (i.e. a version number was specified).

ID: wfs/1.0.0/basic/getcapabilities/get/5
Class: A
Text: When a GetCapabilities request is made against basic WFS, the reponse cabilities document must define capabilities entries for the request GetCapabilities for HTTP GET, DescribeFeatureType for HTTP GET or POST and GetFeature for HTTP GET or POST. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The response document will be tested to check that the capabilities document defines the capabilities requests GetCapabilities for HTTP GET, DescribeFeature for HTTP GET or POST and GetFeature for HTTP GET or POST. This test does not test that the capabilities advertised actually work, this is done in other tests.

ID: wfs/1.0.0/basic/getcapabilities/get/6
Class: A
Text: When a wfs:GetCapabilities request is made, the result document must contain a schema description language of XMLSCHEMA for DescribeFeatureType. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test.The response document will be tested to check that the DescribeFeatureType request has a SchemaDescriptionLanguage of XMLSCHEMA.

ID: wfs/1.0.0/basic/getcapabilities/get/7
Class: A
Text: When a wfs:GetCapabilities request is made, the result document must contain a result format of GML2 for GetFeature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test.The response document will be tested to check that the GetFeature request has a ResultFormat of GML2.

ID: wfs/1.0.0/basic/getcapabilities/get/8
Class: A
Text: When a wfs:GetCapabilities request is made to a basic WFS, the result document must define the Query operation either globally or for at least one feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test.The response document will be tested to check that the global FeatureTypeList or at least one FeatureType defines the Query Operation.

getCapabilitiesPost - GetCapabilities over HTTP POST Tests

ID: wfs/1.0.0/basic/getcapabilities/post/1
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made for a version number that the server supports, the result document must be a wfs:WFS_Capabilities with the version number equal to the version number in the request. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will define the version number to be 1.0.0. The response document will be tested to check that the version number returned in the capabilities document is the same as the requested version.

ID: wfs/1.0.0/basic/getcapabilities/post/2
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made for a version number that is greater than the version the server supports, the result document must be a wfs:WFS_Capabilities with the version number equal to the highest version number that the server supports which is less than the requested version number. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will define the version number to be 99.99.99. The response document will be tested to check that the version number returned in the capabilities document is less than 99.99.99.

ID: wfs/1.0.0/basic/getcapabilities/post/3
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made for a version number that is less than the version the server supports, the result document must be a wfs:WFS_Capabilities with the version number equal to the lowest version number that the server supports which is greater than the requested version number. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will define the version number to be 0.99.99. The response document will be tested to check that the version number returned in the capabilities document is greater than 0.99.99.

ID: wfs/1.0.0/basic/getcapabilities/post/4
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made without specifying a version number, the result document must be a wfs:WFS_Capabilities with the version number equal to the highest version number that it supports. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The request will noy define a version number. The response document will be tested to check that the version number returned in the capabilities document is greater than 0.0.0 (i.e. a version number was specified).

ID: wfs/1.0.0/basic/getcapabilities/post/5
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a GetCapabilities request is made against basic WFS, the reponse cabilities document must define capabilities entries for the request GetCapabilities for HTTP GET, DescribeFeatureType for HTTP GET or POST and GetFeature for HTTP GET or POST. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test. The response document will be tested to check that the capabilities document defines the capabilities requests GetCapabilities for HTTP GET, DescribeFeature for HTTP GET or POST and GetFeature for HTTP GET or POST. This test does not test that the capabilities advertised actually work, this is done in other tests.

ID: wfs/1.0.0/basic/getcapabilities/post/6
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made, the result document must contain a schema description language of XMLSCHEMA for DescribeFeatureType. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test.The response document will be tested to check that the DescribeFeatureType request has a SchemaDescriptionLanguage of XMLSCHEMA.

ID: wfs/1.0.0/basic/getcapabilities/post/7
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made, the result document must contain a result format of GML2 for GetFeature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test.The response document will be tested to check that the GetFeature request has a ResultFormat of GML2.

ID: wfs/1.0.0/basic/getcapabilities/post/8
Class: C
Scope: The Server supports WFS GetCapabilities operations over HTTP POST.
Text: When a wfs:GetCapabilities request is made to a basic WFS, the result document must define the Query operation either globally or for at least one feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section GetCapabilities]
Note: This test issues a GetCapabilities request using HTTP GET to the WFS server under test.The response document will be tested to check that the global FeatureTypeList or at least one FeatureType defines the Query Operation.

describeFeatureType - DescribeFeatureType Tests

There are no testable assertions in this section.

describeFeatureTypeGet - DescribeFeatureType over HTTP GET Tests

ID: wfs/1.0.0/basic/describefeaturetype/get/1
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made without the outputFormat specified, the result document must be an GML XML Schema document. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will not include the outputFormat attribute. The response document will be tested to check that the root element is a xs:schema element and that it conforms to the GML rules.

ID: wfs/1.0.0/basic/describefeaturetype/get/2
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with the outputFormat XMLSCHEMA, the result document must be an GML XML schema document. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the outputFormat attribute with the value XMLSCHEMA. The response document will be tested to check that the root element is a xs:schema element and that it conforms to the GML rules.

ID: wfs/1.0.0/basic/describefeaturetype/get/3
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with an unsupported outputFormat 'DUMMYFORMAT', the result document must be an ogc:ServiceExceptionReport document. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the outputFormat attribute with the value DUMMYFORMAT. The response document will be tested to check that the root element is an ogc:ServiceExceptionReport document.

ID: wfs/1.0.0/basic/describefeaturetype/get/4
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made without a TypeName, the result document must be an GML XML schema document that describes all feature types served by the WFS. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will not include the typeName. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for one feature type for each of the CITE schemas.

ID: wfs/1.0.0/basic/describefeaturetype/get/5
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with a single TypeName, the result document must be an GML XML schema document that describes the specified feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the typeName cgf:Points. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for cgf:Points feature type.

ID: wfs/1.0.0/basic/describefeaturetype/get/6
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with a multiple TypeNames in the same namespace, the result document must be an GML XML schema document that describes the specified feature types. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the typeName cgf:Points,cgf:Lines. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for cdf:Inserts feature types cgf:Points,cgf:Lines.

ID: wfs/1.0.0/basic/describefeaturetype/get/7
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with a multiple TypeNames in different namespaces, the result document must be an GML XML schema document that describes the specified feature types. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the typeName cgf:Points,cdf:Other. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for cdf:Inserts feature types cgf:Points,cdf:Other.

ID: wfs/1.0.0/basic/describefeaturetype/get/8
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with a single TypeName that does not exist, the result document must be an ogc:ServiceExceptionReport. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the typeName cgf:DummyFeature. The response document will be tested to check that the root element is a ogc:ServiceExceptionReport.

ID: wfs/1.0.0/basic/describefeaturetype/get/9
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP GET.
Text: When a wfs:DescribeFeatureType request is made with multiple TypeNames with one that does not exist, the result document must be an ogc:ServiceExceptionReport. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section KVP.DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP GET to the WFS server under test. The request will include the typeName cgf:Points,cgf:DummyFeature. The response document will be tested to check that the root element is a ogc:ServiceExceptionReport.

describeFeatureTypePost - DescribeFeatureType over HTTP POST Tests

ID: wfs/1.0.0/basic/describefeaturetype/post/1
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made without the outputFormat specified, the result document must be an GML XML Schema document. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will not include the outputFormat attribute. The response document will be tested to check that the root element is a xs:schema element and that it conforms to the GML rules.

ID: wfs/1.0.0/basic/describefeaturetype/post/2
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with the outputFormat XMLSCHEMA, the result document must be an GML XML schema document. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the outputFormat attribute with the value XMLSCHEMA. The response document will be tested to check that the root element is a xs:schema element and that it conforms to the GML rules.

ID: wfs/1.0.0/basic/describefeaturetype/post/3
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with an unsupported outputFormat 'DUMMYFORMAT', the result document must be an ogc:ServiceExceptionReport document. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the outputFormat attribute with the value DUMMYFORMAT. The response document will be tested to check that the root element is an ogc:ServiceExceptionReport document.

ID: wfs/1.0.0/basic/describefeaturetype/post/4
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made without a TypeName, the result document must be an GML XML schema document that describes all feature types served by the WFS. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will not include the typeName. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for one feature type for each of the CITE schemas.

ID: wfs/1.0.0/basic/describefeaturetype/post/5
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with a single TypeName, the result document must be an GML XML schema document that describes the specified feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the typeName cgf:Points. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for cgf:Points feature type.

ID: wfs/1.0.0/basic/describefeaturetype/post/6
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with a multiple TypeNames in the same namespace, the result document must be an GML XML schema document that describes the specified feature types. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the typeName cgf:Points,cgf:Lines. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for cdf:Inserts feature types cgf:Points,cgf:Lines.

ID: wfs/1.0.0/basic/describefeaturetype/post/7
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with a multiple TypeNames in different namespaces, the result document must be an GML XML schema document that describes the specified feature types. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the typeName cgf:Points,cdf:Other. The response document will be tested to check that the root element is a xs:schema element, it conforms to the GML rules and contains definitions for cdf:Inserts feature types cgf:Points,cdf:Other.

ID: wfs/1.0.0/basic/describefeaturetype/post/8
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with a single TypeName that does not exist, the result document must be an ogc:ServiceExceptionReport. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the typeName cgf:DummyFeature. The response document will be tested to check that the root element is a ogc:ServiceExceptionReport.

ID: wfs/1.0.0/basic/describefeaturetype/post/9
Class: C
Scope: The Server supports WFS DescribeFeatureType operations over HTTP POST.
Text: When a wfs:DescribeFeatureType request is made with multiple TypeNames with one that does not exist, the result document must be an ogc:ServiceExceptionReport. [OpenGISB. Web Feature Service Implementation Specification 1.0.0 section DescribeFeatureType]
Note: This test issues a wfs:DescribeFeatureType request using HTTP POST to the WFS server under test. The request will include the typeName cgf:Points,cgf:DummyFeature. The response document will be tested to check that the root element is a ogc:ServiceExceptionReport.

basicGetFeature - GetFeature tests

There are no testable assertions in this section.

basicGetFeatureGet - GetFeature tests (GET)

ID: wfs/1.0.0/basic/getfeature/get/1
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that a GetFeature request with the output format GML2 returns a wfs:FeatureCollection with GML data. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The outputFormat attribute defines the format to use to generate the result set. The default value is GML2 indicating that GML [2] shall be used.

ID: wfs/1.0.0/basic/getfeature/get/2
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that a GetFeature request with no output format defined returns a wfs:FeatureCollection with GML data. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The outputFormat attribute defines the format to use to generate the result set. The default value is GML2 indicating that GML [2] shall be used.

ID: wfs/1.0.0/basic/getfeature/get/3
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that a GetFeature request with an non supported output format defined returns a wfs:FeatureCollection with GML data. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The outputFormat attribute defines the format to use to generate the result set. The default value is GML2 indicating that GML [2] shall be used. Vendor specific formats (including non-XML and binary formats), declared in the capabilities document are also possible.

ID: wfs/1.0.0/basic/getfeature/get/4
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that getting the single feature of type cdf:Other returns the specified and all the mandatory properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: In the event that a WFS encounters a query that does not select all mandatory properties of a feature, the WFS will internally augment the property name list to include all necessary property names.

ID: wfs/1.0.0/basic/getfeature/get/5
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that they query for the feature type cdf:Fifteen returns all 15 features in the database. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: If no "Filter" element is contained within the "Query" element, then the query is unconstrained and all feature instances should be retrieved.

ID: wfs/1.0.0/basic/getfeature/get/6
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that they query for the feature types cdf:Fifteen and cdf:Seven returns all 15 With an unsupported output format and 7 features in the database. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The "GetFeature" element contains one or more "Query"; elements, each of which in turn contain the description of a query. The results of all queries contained in a GetFeature request are concatenated to produce the result set.

ID: wfs/1.0.0/basic/getfeature/get/7
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that they query for the feature type cdf:Fifteen with a maxFeatures of 10 returns only 10 items. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The optional maxFeatures attribute can be used to limit the number of features that a GetFeature request retrieves. Once the maxFeatures limit is reached, the result set is truncated at that point.

ID: wfs/1.0.0/basic/getfeature/get/8
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that they query for the feature types cdf:Fifteen and cdf:Seven with a maxFeatures of 20 returns 15 and 5 features respectively. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The optional maxFeatures attribute can be used to limit the number of features that a GetFeature request retrieves. Once the maxFeatures limit is reached, the result set is truncated at that point.

ID: wfs/1.0.0/basic/getfeature/get/9
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that getting the single feature of type cdf:Other returns all of the properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: If no "PropertyName" elements are specified, then all feature properties should be fetched.Test that they query for the feature types cdf:Fifteen and cdf:Seven with a maxFeatures of 20 returns 15 and 5 features respectively.

ID: wfs/1.0.0/basic/getfeature/get/10
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP GET.
Text: Test that getting the single feature of type cdf:Other returns all of the properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The "PropertyName" element is used to enumerate the feature properties that should be selected during a query and whose values should be included in the response to a GetFeature request.

basicGetFeaturePost - GetFeature tests (POST)

ID: wfs/1.0.0/basic/getfeature/post/1
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that a GetFeature request with the output format GML2 returns a wfs:FeatureCollection with GML data. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The outputFormat attribute defines the format to use to generate the result set. The default value is GML2 indicating that GML [2] shall be used.

ID: wfs/1.0.0/basic/getfeature/post/2
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that a GetFeature request with no output format defined returns a wfs:FeatureCollection with GML data. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The outputFormat attribute defines the format to use to generate the result set. The default value is GML2 indicating that GML [2] shall be used.

ID: wfs/1.0.0/basic/getfeature/post/3
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that a GetFeature request with no output format defined returns a wfs:FeatureCollection with GML data. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The outputFormat attribute defines the format to use to generate the result set. The default value is GML2 indicating that GML [2] shall be used. Vendor specific formats (including non-XML and binary formats), declared in the capabilities document are also possible.

ID: wfs/1.0.0/basic/getfeature/post/4
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that getting the single feature of type cdf:Other returns the specified and all the mandatory properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: In the event that a WFS encounters a query that does not select all mandatory properties of a feature, the WFS will internally augment the property name list to include all necessary property names.

ID: wfs/1.0.0/basic/getfeature/post/5
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that they query for the feature type cdf:Fifteen returns all 15 features in the database. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: If no "Filter" element is contained within the "Query" element, then the query is unconstrained and all feature instances should be retrieved.

ID: wfs/1.0.0/basic/getfeature/post/6
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that they query for the feature types cdf:Fifteen and cdf:Seven returns all 15 With an unsupported output format and 7 features in the database. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The "GetFeature" element contains one or more "Query"; elements, each of which in turn contain the description of a query. The results of all queries contained in a GetFeature request are concatenated to produce the result set.

ID: wfs/1.0.0/basic/getfeature/post/7
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that they query for the feature type cdf:Fifteen with a maxFeatures of 10 returns only 10 items. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The optional maxFeatures attribute can be used to limit the number of features that a GetFeature request retrieves. Once the maxFeatures limit is reached, the result set is truncated at that point.

ID: wfs/1.0.0/basic/getfeature/post/8
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that they query for the feature types cdf:Fifteen and cdf:Seven with a maxFeatures of 20 returns 15 and 5 features respectively. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The optional maxFeatures attribute can be used to limit the number of features that a GetFeature request retrieves. Once the maxFeatures limit is reached, the result set is truncated at that point.

ID: wfs/1.0.0/basic/getfeature/post/9
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that getting the single feature of type cdf:Other returns all of the properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: If no "PropertyName" elements are specified, then all feature properties should be fetched.Test that they query for the feature types cdf:Fifteen and cdf:Seven with a maxFeatures of 20 returns 15 and 5 features respectively.

ID: wfs/1.0.0/basic/getfeature/post/10
Class: C
Scope: The Server supports WFS GetFeature operations over HTTP POST.
Text: Test that getting the single feature of type cdf:Other returns all of the properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The "PropertyName" element is used to enumerate the feature properties that should be selected during a query and whose values should be included in the response to a GetFeature request.

basicGetFeatureComplex - GetFeature with complex values tests

There are no testable assertions in this section.

basicGetFeatureComplexGet - GetFeature with complex values tests (GET)

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/1
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: When a wfs:GetFeature request with a property name with a numerical predicate, the result document must contain the property with that index. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: This test issues a wfs:GetFeature request using HTTP GET to the WFS server under test. The request includes a property name with a numerical xpath predicate to return the second value of the repeated resident property. The response document will be tested to check that the search feature returned contains the value 'Beth'.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/2
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a numerical predicate and the feature prefix to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: Each step in the path may optionally contain a predicate composed of the predicate delimiters '[' and ']' and a number indicating which child of the context node is to be selected. This allows feature properties that may be repeated to be specifically referenced. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/3
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: Test that getting the single feature of type ccf:Complex returns all of the properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The "PropertyName" element is used to enumerate the feature properties that should be selected during a query and whose values should be included in the response to a GetFeature request.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/4
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with an attribute axis and the feature prefix to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The final step in a path may optionally be composed of the abbreviated form of the attribute:: axis specifier, '@', and the name of a feature property encoded as the principal node type of attribute. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/5
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with an attribute axis to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The final step in a path may optionally be composed of the abbreviated form of the attribute:: axis specifier, '@', and the name of a feature property encoded as the principal node type of attribute. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/6
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a single step in the path to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/7
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a single step in the path and the feature prefix to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/8
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a multiple steps in the path to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: Relative location paths are composed of one or more steps separated by the path separator '/'.

ID: wfs/1.0.0/basic/getfeature/complexvalue/get/9
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a multiple steps in the path and the feature prefix to check that the property is returned. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: Relative location paths are composed of one or more steps separated by the path separator '/'.

basicGetFeatureComplexPost - GetFeature with complex values tests (POST)

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/1
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: When a wfs:GetFeature request with a property name with a numerical predicate, the result document must contain the property with that index. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: This test issues a wfs:GetFeature request using HTTP POST to the WFS server under test. The request includes a property name with a numerical xpath predicate to return the second value of the repeated resident property. The response document will be tested to check that the search feature returned contains the value 'Beth'.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/2
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a numerical predicate and the feature prefix to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: Each step in the path may optionally contain a predicate composed of the predicate delimiters '[' and ']' and a number indicating which child of the context node is to be selected. This allows feature properties that may be repeated to be specifically referenced. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/3
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: Test that getting the single feature of type ccf:Complex returns all of the properties defined in the schema for that feature type. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The "PropertyName" element is used to enumerate the feature properties that should be selected during a query and whose values should be included in the response to a GetFeature request.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/4
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with an attribute axis and the feature prefix to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The final step in a path may optionally be composed of the abbreviated form of the attribute:: axis specifier, '@', and the name of a feature property encoded as the principal node type of attribute. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/5
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with an attribute axis to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The final step in a path may optionally be composed of the abbreviated form of the attribute:: axis specifier, '@', and the name of a feature property encoded as the principal node type of attribute. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/6
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a single step in the path to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/7
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a single step in the path and the feature prefix to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/8
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a multiple steps in the path to check that the property is returned. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: Relative location paths are composed of one or more steps separated by the path separator '/'.

ID: wfs/1.0.0/basic/getfeature/complexvalue/post/9
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the feature properties with complex values
Text: This test requests a PropertyName with a multiple steps in the path and the feature prefix to check that the property is returned. The first step of a relative location path may correspond to the root element of the feature property being referenced or to the root element of the feature type with the next step corresponding to the root element of the feature property being referenced. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: Relative location paths are composed of one or more steps separated by the path separator '/'.

basicGetFeatureFilter - GetFeature filter tests

There are no testable assertions in this section.

basicGetFeatureFilterArithmetic - GetFeature arithmetic operators tests

There are no testable assertions in this section.

basicGetFeatureFilterArithmeticGet - GetFeature arithmetic operators tests (GET)
ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/get/1
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the arithmetic operators.
Text: Test adding the two literals 4 & 3 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element encodes the operation of addition and contains the arguments which can be any expression that validates according to this specification.

ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/get/2
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the arithmetic operators.
Text: Test subtracting the two literals 10 & 3 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element encodes the operation of subtraction where the second argument is subtracted from the first. The element contains the argument when can be any expression that validates according to this specification.

ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/get/3
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the arithmetic operators.
Text: Test multiplying the property cdf:integers by 1 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element encodes the operation multiplication. The element contains the two argument to be multiplied which can be any expression that validates according to this specification.

ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/get/4
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the arithmetic operators.
Text: Test dividing the property cdf:integers by 1 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The
element encodes the operation of division where the first argument is divided by the second argument. The
element contains the arguments which can be any valid expression that validates according to this specification. The second argument or expression cannot evaluate to zero.
basicGetFeatureFilterArithmeticPost - GetFeature arithmetic operators tests (POST)
ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/post/1
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the arithmetic operators.
Text: Test adding the two literals 4 & 3 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element encodes the operation of addition and contains the arguments which can be any expression that validates according to this specification.

ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/post/2
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the arithmetic operators.
Text: Test subtracting the two literals 10 & 3 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element encodes the operation of subtraction where the second argument is subtracted from the first. The element contains the argument when can be any expression that validates according to this specification.

ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/post/3
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the arithmetic operators.
Text: Test multiplying the property cdf:integers by 1 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element encodes the operation multiplication. The element contains the two argument to be multiplied which can be any expression that validates according to this specification.

ID: wfs/1.0.0/basic/getfeature/filter/arithmeticoperators/post/4
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP POST.
  • The Server supports the arithmetic operators.
Text: Test dividing the property cdf:integers by 1 is equal to 7 the value of the cdf:integers property of the desired feature. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The
element encodes the operation of division where the first argument is divided by the second argument. The
element contains the arguments which can be any valid expression that validates according to this specification. The second argument or expression cannot evaluate to zero.

basicGetFeatureFilterComparison - GetFeature comparison operators tests

There are no testable assertions in this section.

basicGetFeatureFilterComparisonGet - GetFeature comparison operators tests (GET)
ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/1
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsGreaterThanOrEqualTo operator returns the correct feature for a number comparisson with the value equal to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element is defined as a compact way of encoding a range check. The lower and upper boundary values are inclusive.

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/2
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the between operators.
Text: This test checks that the PropertyIsBetween operator returns the correct feature for a number comparisson with the boundary values set to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element is defined as a compact way of encoding a range check. The lower and upper boundary values are inclusive.

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/3
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the between operators.
Text: This test checks that the PropertyIsBetween operator returns the correct feature for a date comparisson with the boundary values set to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The element is defined as a compact way of encoding a range check. The lower and upper boundary values are inclusive.

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/4
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsBetween operator returns the correct feature for a date comparisson with the boundary values set to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,>=,<=,<>) of comparison operators, this specification defines the elements , and.

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/5
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsEqualTo operator returns the correct feature for a number comparisson with the value set to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/6
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsEqualTo operator returns the correct feature for a date comparisson with the value set to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set <=,<,>,>=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/7
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsGreaterThan operator returns the correct feature for a number comparisson with the value less than the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/8
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsGreaterThan operator returns the correct feature for a date comparisson with the value less than the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/9
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsGreaterThanOrEqualTo operator returns the correct feature for a string comparisson with the value equal to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/10
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsGreaterThanOrEqualTo operator returns the correct feature for a string comparisson with the value equal to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/11
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsGreaterThanOrEqualTo operator returns the correct feature for a string comparisson with the value equal to the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/12
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsLessThan operator returns the correct feature for a string comparisson with the value greater than the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]
Note: The Common Catalog Query Language [4] defines a standard set of comparison operators. In addition to the standard set (=,<,>,<=,<=,<>) of comparison operators, this specification defines the elements , and .

ID: wfs/1.0.0/basic/getfeature/filter/comparisonoperators/get/13
Class: C
Scopes:
  • The Server supports WFS GetFeature operations over HTTP GET.
  • The Server supports the comparison operators.
Text: This test checks that the PropertyIsLessThan operator returns the correct feature for a number comparisson with the value greater than the expected value of the property. [OpenGISB. Web Feature Service Implementation Specification 1.0.0]