Invalid Value for Updated Since Param

Table of Contents

Purpose #

Validates behavior of the server when an invalid updated since date is sent as part of Australian CDR calls. What qualifies as an updated since date? Updated-since is expected to be a valid DateTimeString provided as a Combined Date and Time string as per RFC3339 (labelled date-time in the RFC). As specified in RFC3339 times MUST be offset relative to UTC. To provide an invalid updated-date we provide an invalid value such as test. A specific error is expected.

Spec reference #

Error Codes: https://consumerdatastandardsaustralia.github.io/standards/#error-codes
Common Field Types: https://consumerdatastandardsaustralia.github.io/standards/#common-field-types

Checks #

Response is returned
Status code
Error body
Error message

Expects #

Status code of 400
Response body containing
- error title Invalid Date
- error code urn:au-cds:error:cds-all:Field/InvalidDateTimeDateTime
- error detail a human readable message

{
    errors: [
        {
            code: 'urn:au-cds:error:cds-all:Field/InvalidDateTime',
            detail: 'A detailed description',
            title: 'Invalid Date'
        }
    ]
}

Messages #

Endpoint did not respond with errors when a bad updated-since was sent: Returned when the server returned an empty response.

No Error body returned on error response: Returned when the server responded with an empty body.

Unexpected error status, expected 400, got XXX: Returned when the status was not 400 as expected but instead returned the value specified.

An error with code: urn:au-cds:error:cds-all:Field/InvalidDateTime and title Invalid Date is expected to be returned: Returned when the response body contains a different error code or title than those expected.