Invalid Version
Table of Contents
Purpose #
Validates behavior of the server when an invalid minimum version is sent as part of Australian CDR calls. What qualifies as an invalid version? Any version that is greater than 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.
If the value of x-min-v is equal to or higher than the value of x-v then the x-min-v header should be treated as absent.
Spec reference #
- Error Codes
- https://consumerdatastandardsaustralia.github.io/standards/#error-codes
- Http Headers
- https://consumerdatastandardsaustralia.github.io/standards/#http-headers
Checks #
- Response is returned
- Status code
- Error body
- Error message
Expects #
- Status code of 200
- Response body the valid data
In this scenario, it is expected that the server treats the x-min-v header as absent when it is greater than the x-v header.
Messages #
- Endpoint did not respond with data when a bad x-min-v was sent
- Returned when the service returns an error response rather than the expected data type.
- No Error body returned on error response
- Returned when the server responded with an empty body.
- Unexpected error status, expected 200, got XXX
- Returned when the status was not 200 as expected but instead returned the value specified.