In testsuite , all scenarios of /v1/update-operation-key :: reference core-model-1-4:control-construct :: Tests::
Existing logic:
We are collecting a random operationClientLtp from a randomHttpClientLtp and storing it in collectionVariables for proceeding requests where we populate values for request-body of /v1/update-operation-key.
Problem:
Few http-clients in contrl-construct does not have a operation-cllient ltp. This passes an empty operationCLientLtp object to the proceeding requests. This results in the request-body being filled with "undefined". This causes 400 bad request error.
Solution:
In all reference core-model-1-4:control-construct :: Tests, we have to modify the functions supporting to get operationClientLtp shall be modified to extract a valid httpClientLtp (httpCLientLtp containing atleast one client-ltp) and a valid OperationClientLtp (operation-key length > 5)
In testsuite , all scenarios of /v1/update-operation-key :: reference core-model-1-4:control-construct :: Tests::
Existing logic:
We are collecting a random operationClientLtp from a randomHttpClientLtp and storing it in collectionVariables for proceeding requests where we populate values for request-body of /v1/update-operation-key.
Problem:
Few http-clients in contrl-construct does not have a operation-cllient ltp. This passes an empty operationCLientLtp object to the proceeding requests. This results in the request-body being filled with "undefined". This causes 400 bad request error.
Solution:
In all reference core-model-1-4:control-construct :: Tests, we have to modify the functions supporting to get operationClientLtp shall be modified to extract a valid httpClientLtp (httpCLientLtp containing atleast one client-ltp) and a valid OperationClientLtp (operation-key length > 5)