adding logs to deal with negative case scenarios
Adding logs such that for any 4xx or 5xx calls we are able to trace the flow using correlation id, urls, http methods, which will enable us to perform the debugging faster and also at the places where we are blocked because of no correlation id
ADME instance compatibility: in azure/m16-master 5 test fail with adme instance, under the same circumstances 7 test cases fail by our changes as we have changed 2 test cases Assert conditions, and these fail in local because of repetitive subscription creation
- azure/m16-master :
- current branch:
Test scenarios tested:
- 401 unauthorized:
getting such request sent:
and this is response received:
response body with correlation id:
- Socket timeout:
request sent and the stack trace of error,socket timeout exception error and the response received after the retry:
Edited by Harshika Dhoot