refactor:setting time stamp for response only after verified response

[shivamsouravjha]

Related Issue

• Instead of using an array to save the response time reverted to set the response time of response only after the data is verified.
  Closes: [bug]: Gin-mongo throwing error in Test mode in POST calls  #1418

Describe the changes you've made

Because of maintaining an array of mock and picking the first element of the array we were unable to get certain mock files as a result of which connection would end and test cases would fail.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Please let us know if any test cases are added

Please describe the tests(if any). Provide instructions how its affecting the coverage.

Describe if there is any unusual behaviour of your code(Write NA if there isn't)

A clear and concise description of it.

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

Screenshots (if any)

[charankamarapu]

Looks good to me but Can you explain why is the last chuck timestamp approach is not implemented? Like maintaining an array and instead of first timestamp taking the last one.

[shivamsouravjha]

Seems like there is only one element in the array, I tried with the above approach yet it didn't work , seems there has to be some more debug needed to use that approach, as of now this PR will fix the current ongoing issue.

[charankamarapu]

ship it!