Demystifying Error response

 So, I was looking into a bug in which my client was complaining that they are getting a generalized error message and specific message relating to that error was absent. So, I did an initial code analysis and found that the log was returned by us, but we are also sending using up an err message from backend and seems like that was coming to be as empty. 

So, what can I do to mitigate it?

  1. I can raise it to my backend team.
  2. Check backends team code and figure out if something is going wrong during the parsing or mapping the response.
  3. Can something specific be added inside my code??
    1. Things are breaking from backends' side so probably I might not be knowing the reason behind it. Unless I get it from backend.
So, after going through the code investigating more, I found that point 2 was valid the issue was with parsing/mapping of response. So, I fixed it up and wrote verification test and raise a pull request.

Comments

Popular posts from this blog

Kustov query language

Making all service APi's generic

How I learned LINQ query Fundamentals