Closed ClemensEmme closed 5 months ago
So this is not quite working this way in the actual tests. If you look at the commit attached to this issue. There was a issue about this a few months ago that was fixed. Try upgrading to 4.2.7
Works like a charm, thanks a lot. I didn't know we on a kinda deprecated version. Will close the Issue.
Describe the bug When creating a test, that registers two mocked responses for the same route, but different http methods, the mock always triggers the first registered behavior.
To Reproduce
Expected behavior As far as I understand the examples (and the part of the internal implementation) I could not find a reason for this behavior. My expectation was, that method and route act as two separate keys for mocking the Unirest client. I couldn't find an example in the provided demo of this repository. If there is something I missed, please explain it to me or give me a link. Im feeling like missing the point by a mile, even while standing right in front of the solution. If I get RTFMed on this, I probably deserve it.
Environmental Data:
Additional context Stacktrace: