Test operation

Requests as well as responses can use the IsTest element. This indicator is intended to allow testing of client implementations and investigation of possible errors in the interplay between involved components without triggering business transactions. To ensure this, the following rules apply to a Veloconnect-compliant server and its operator:

Rule: Test operationgel:

  1. Anyone with a legitimate interest in using the Veloconnect interface must be granted access to it within a reasonable time. Whether the interest is legitimate is decided on an individual basis by the server's operator. Development of a Veloconnect interface for a client usually gives rise to a legitimate interest. Access may be limited to a reasonable period of time, and may require the interested party to commit to confidentiality and use access only for the purposes stated.

  2. If the IsTest element is not used in a request or response, it is equivalent to using this element with content set to false.

  3. The IsTest elements in the request and response forming part of an operation have the same value. If this value is true, the operation is considered a test.

  4. In a transaction, an operation performed as a test must not be followed or preceded by an operation not performed as a test. If the client sends a request which conflicts with this, the server must return error code 435.

  5. An operation performed as a test must not trigger business transactions between buyer and seller.

  6. The responses which a server returns in a test operation do not differ from those in the same operation not performed as a test, unless this is necessary to comply with the previous rule.

 

The IsTest flag is only relevant in transaktion order, and here only in the FinishOrder operation, because this involves the distinction between whether or not an order is actually executed.

For all other transactions or operations, there is ultimately no difference between whether IsTest= true or IsTest=false.