Non-date x-fapi-auth-date

Purpose #

Validates behavior of the server when a non-date x-fapi-auth-date is sent as part of Australian CDR calls. What counts as a non-date request? In this case we use a string value such as test for the x-fapi-auth-date. It is expected that this would fail.

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 400
2. Response body containing
   • error title Invalid Date
   • error code urn:au-cds:error:cds-all:Field/InvalidDateTime
   • 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 x-fapi-auth-date 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.