Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not supporting multiple PATCH method requests. #93

Closed
singh-virendra opened this issue Apr 13, 2018 · 2 comments · Fixed by #126
Closed

Not supporting multiple PATCH method requests. #93

singh-virendra opened this issue Apr 13, 2018 · 2 comments · Fixed by #126
Assignees
Labels
bug done something is finished

Comments

@singh-virendra
Copy link

I tried to put multiple patch requests in response.yaml, which is not working as expected(as it works for PUT and POST).

response.yaml

-
  request:
    method: PATCH
    url: /simulator/content/v1/url1
    file: response/service/failure-request.json
  response:
    status: 404

-
  request:
    method: PATCH
    url: /simulator/content/v1/url1
  response:
    status: 200
    headers:
      content-type: application/json
    file: response/service/success.json

failure-request.json

{
  "identifier": {
    "identifierTyp": "IDENTIFIER",
    "identifierVal": "1234567890"
  },
  "permissions": {
    "PERMISSION.PERMISSION1": {
      "value": "ABC"
    }
  },
  "extra": {
    "extraId": "54"
  }
}

success.json

{
  "description": "Queued",
  "transactionId": "123-456-789"
}

Expected: It should return the response with 200, if no body is present while making request to url /simulator/content/v1/url1, else if the body failure-request.json is present then it should return 404 response.

Actual: it returns the status for which the entry is present first in the file response.yaml.

@azagniotov
Copy link
Owner

Fixed in v6.0.1

azagniotov added a commit that referenced this issue Apr 15, 2018
Fixes #93: Considering PATCH method when evaluating if request body stubbed
@singh-virendra
Copy link
Author

It's not working as expected. Even already working flows stopped working now. Opening new issue with logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug done something is finished
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants