Invalid Value for Effective Parameter

Table of Contents

Purpose #

Validates behavior of the server when an invalid value is sent for the effective param as part of Australian CDR calls. What is an invalid effective param? Effective param is an ENUM with value of CURRENT, FUTURE and ALL. For this test we pass an alternate value such as test. The server is expected to respond with an error.

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 Field
- error code urn:au-cds:error:cds-all:Field/Invalid
- error detail a human readable message

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

Messages #

Endpoint did not respond with errors when a bad effective 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/Invalid and title Invalid Field is expected to be returned: Returned when the response body contains a different error code or title than those expected.