Expecting calls to the same path in the same test

[ybce]

I have a scenario where I am setting up expectations to call an external service twice (mocking that in my tests using mock-https-server), one which returns an empty array and one that returns a response.

something like this:

  expectGetResourceByParamX (queryParams, statusCode, body) {
    this.server.on({
      method: 'GET',
      path: '/v1/resource',
      filter: (req) => {
       // filter code
        return true
      },
      reply: {
        status: statusCode,
        headers: { 'content-type': 'application/json' },
        body: JSON.stringify(body)
      }
    })
  }

  expectGetResourceByParamY (queryParams, statusCode, body) {
    this.server.on({
      method: 'GET',
      path: '/v1/resource',
      filter: (req) => {
       // filter code
        return true
      },
      reply: {
        status: statusCode,
        headers: { 'content-type': 'application/json' },
        body: JSON.stringify(body)
      }
    })
  }

The only difference is what query params I use on that same exact path, however when setting up the test this seems to cause an issue since the handlers have the same path and the requests that come in are processed by the wrong handler. I looked at the library code but can't see an obvious place where this can be fixed.

Any ideas on how this sort of problem can be solved (if it can be) using this library or is this some sort of limitation of the library.

Thank You.

[ybce]

I just looked at the pull requests in the repo and this #1 might be something that can help with my issue.

[pracucci]

I'm not sure I'm getting your use case. In the example provided, the two functions expectGetResourceByParamX() and expectGetResourceByParamY() are identical, but I would expect in the real world to differ. Depending on how they differ, you may end up with a different solution.

Generally speaking, I would suggest you to look at the fact that the body can also be specified as body: function(req) {}: this way you can dinamically generate the response based on the request, but you can also keep track of each received request for later inspection / assertion on it.