-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
Request body is missing in generated pact file for requests that include matching on request body #788
Labels
Comments
The only possible solution would be that I deserialize the value from the matcher ( {
"consumer": {
"name": "Consumer1"
},
"interactions": [
{
"providerState": "Example1",
"request": {
"method": "POST",
"path": "/foo",
"body": {
"name" : "john"
}
},
"response": {
"status": "201",
}
}
],
"provider": {
"name": "Provider1"
}
} Another option would be that you can add an example body like: server
.Given(Request.Create().UsingPost().WithPath("/foo")
.WithBody(new JsonPartialMatcher(@"{ ""name"": ""john"" }"))).WithExample( ... todo ...) |
@shack05 |
Hi @StefH, thank you, preview 1.5.3-ci-16359 works like a charm. |
@shack05 Thanks for testing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The request body is missing in generated pact file for requests that include matching on request body.
More specifically, I am using the JsonPartialMatcher.
Expected behavior:
The generated pact file includes the expectations of the request body as specified by the matchers used in the wiremock scenario.
Test to reproduce
I'm not sure what the expected pact should look like, but I imagine request body should be included in some way.
The actual pact file is:
Other related info
WIremock version - 1.5.3-ci-16331 (from #784).
The text was updated successfully, but these errors were encountered: