↓Skip to main content
  1. Data-holder-testings/
  2. Validations/

Invalid Version

Table of Contents

Purpose #

Validates behavior of the server when an invalid version is sent as part of Australian CDR calls. What qualifies as an invalid version? Any version that is not the current version for this endpoint. For the purposes we use N-1 for the version, where N is the current valid version. This way we are likely to validate a previous version that is no-longer valid.

Spec reference #

Error Codes
https://consumerdatastandardsaustralia.github.io/standards/#error-codes
Http Headers
https://consumerdatastandardsaustralia.github.io/standards/#http-headers

Checks #

  1. Response is returned
  2. Status code
  3. Error body
  4. Error message

Expects #

  1. Status code of 406
  2. Response body containing
    • error title Unsupported Version
    • error code urn:au-cds:error:cds-all:Header/UnsupportedVersion
    • error detail a human readable message
{
    errors: [
        {
            code: 'urn:au-cds:error:cds-all:Header/UnsupportedVersion',
            detail: 'A detailed description',
            title: 'Unsupported Version'
        }
    ]
}

Messages #

Endpoint returned with data when an invalid x-v was sent
Returned when the service returns a result when an error response is expected.
No Error body returned on error response
Returned when the server responded with an empty body.
Unexpected error status, expected 406, got XXX
Returned when the status was not 406 as expected but instead returned the value specified.
An error with code: urn:au-cds:error:cds-all:Header/UnsupportedVersion and title Unsupported Version is expected to be returned
Returned when the response body contains a different error code or header than those expected.
↑