Skip to content

adding logs to deal with negative case scenarios

Harshika Dhoot requested to merge registerLogs into azure/m18-master

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

  1. azure/m16-master : registeradmem16
  2. current branch: registeradme

Test scenarios tested:

  1. 401 unauthorized: getting such request sent:register401response and this is response received:register401response response body with correlation id:registerresponsebody
  2. Socket timeout: request sent and the stack trace of error,socket timeout exception error and the response received after the retry:registersocket
Edited by Harshika Dhoot

Merge request reports