CME-513: Fix pact for consumer: xui_webApp and providers: acc_manageCaseAssignment, acc_manageCaseAssignment_Noc - #5320
CME-513: Fix pact for consumer: xui_webApp and providers: acc_manageCaseAssignment, acc_manageCaseAssignment_Noc#5320anthonyb-cgi wants to merge 18 commits into
Conversation
…aseAssignment, acc_manageCaseAssignment_Noc
…DSL for defining consumer-provider interactions.
… email fields according to consumer expectations.
…geCaseAssignment_Noc.
…ovider names: 'acc_manageCaseAssignment, acc_manageCaseAssignment_Noc’ in the pact tests.
…or provider API's with provider names: acc_manageCaseAssignment, acc_manageCaseAssignment_Noc.
…ed by the consumer.
…c_manageCaseAssignment.
…ectation of provider acc_manageCaseAssignment.
| headers: { | ||
| 'Content-Type': 'application/json', | ||
| }, | ||
| body: mockResponse, |
There was a problem hiding this comment.
why body is not validated here?
There was a problem hiding this comment.
Good question - as far as I can tell the real EXUI consumer API client doesn't use the provider response body field status_message when successfully calling it. Therefore, I have omitted validation of it from the pact (there used to be pact validation of the body previously when the consumer pact tests weren't testing against the real consumer API client).
However, if the response is rejected the real consumer API client does read the the API response so will check that.
There was a problem hiding this comment.
Here is the new commit I made to cover consumer API consumption of the provider error response body:
d71d6ac
kiran-yenigala-hmcts
left a comment
kiran-yenigala-hmcts
left a comment
There was a problem hiding this comment.
One comment added
2 participants
Jira link
See CME-513
Change description
EXUI Consumer Pact tests were updated to support AAC Case Assignment provider verification by:
shared_withidam_idfields to ensure contract compliance.case_title/caseTitlecoverage for case-assignment responses.