Method case causes unmached requests

[josephdpurcell]

The method that gets specified in the mock file must match the case that is specified in the application.

Angular Request

$http({
  method: 'get',
  url: '/api/v1.0/access-token',
  headers: {
    'Authorization': 'Basic dXNlcm5hbWU6cGFzc3dvcmQ='
  }
})

Mock File

{
  "request": {
    "method": "GET",
    "path": "/api/v1.0/access-token",
    "headers": {
      "Authorization": "Basic dXNlcm5hbWU6cGFzc3dvcmQ="
    }
  },
  "response": {
    "access_token": "P6AlGY9SZSUlw3K0bZteiTp32UP-IOYv49aJNDWZbKQ",
    "type": "Bearer",
    "expires_in": 72204,
    "refresh_token": "u8iBLUb6-sPttALigZZRS4wC-uAuICEd3-8iohDXeiU"
  }
}

Conclusion

I think expecting the writer of the mock to use the same case as is used in the Angular app isn't completely unreasonable, but it should be communicated to the developer that is the case.

What are your thoughts?

[atecarlos]

Hi @josephdpurcell . Yes, actually, I completely expect the plugin to ignore the case. I have a few examples and specs that check that this is working. Perhaps, there is something else that is causing this to not match?

[josephdpurcell]

Yes, apologies, it looks like this is not an issue.