Commit 70f61034 authored by Ken Zangelin's avatar Ken Zangelin
Browse files

fix: 039_05_01 expects InvalidRequest, not BadRequestData, per § 5.5.5 

Section 5.5.5 of v1.9.1 says:

  'If the request payload body is not a valid JSON document then an
  error of type InvalidRequest shall be raised.'

The fragment file used by 039_05_01 (subscription-update-invalid-json.json)
contains a deliberately malformed JSON body — exactly the case the spec
mandates be reported as InvalidRequest, not BadRequestData (which the
spec reserves for *valid* JSON whose contents fail validation against
the API data type or @context, § 5.5.4).

Switch the expected problem type to ERROR_TYPE_INVALID_REQUEST.
parent 3af4f190

TP/NGSI-LD/ContextSource/RegistrationSubscription/UpdateContextSourceRegistrationSubscription/039_05.robot

+1 −1
Original line number Diff line number Diff line
@@ -25,7 +25,7 @@ ${subscription_update_fragment_file_path}= csourceSubscriptions/fragments/s 
    Check Response Status Code    400    ${response.status_code}

    Check Response Body Containing ProblemDetails Element

    ...    response_body=${response.json()}

    ...    problem_type=${ERROR_TYPE_BAD_REQUEST_DATA}

    ...    problem_type=${ERROR_TYPE_INVALID_REQUEST}





*** Keywords ***