-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 Recording Post Body #49
Comments
Do you mean when recording stubs, POST/PUT request bodies should be captured and used as the resulting matching criteria (in addition to URL + method)? |
yes |
I'll add it to the backlog |
great. It doesn't have to be perfect for the first pass. I have a done a quick two hour hack that's not worth sending you. It just adds the body to the mapping file then does some fixup to the json to format it correctly. I also have some stuff that allows you to test with or without recording by setting a boolean, and renames the random mapping file to the junit classname-testname so you know at the end what test recorded that file. |
It also automagicallly starts and stops the proxy recorder on windows, linux or mac. |
I should mention that I'm quite busy with other stuff at the moment, so I'm unlikely to get to this any time soon. If you wanted to polish your changes a bit and ensure there were some decent tests, I'd happily consider a pull request. |
yeah I'm kinda busy too. and your code is so nice, I would hate to hack it up with anything stupid. |
Request body is now recorded if present |
cool thanks |
Enable the 3.x beta documents publishing flow
This is a feature request. It would be nice if we could record post body strings. We have the body in the response right before we create the mapping into json. If we send it along then add a little medicine to the json creation we should be good to go.
The text was updated successfully, but these errors were encountered: