-
Notifications
You must be signed in to change notification settings - Fork 330
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
Adding docs about MockSerializationResult. #960
Adding docs about MockSerializationResult. #960
Conversation
@@ -93,6 +93,42 @@ | |||
|
|||
Note que qualquer chamada do tipo `result.use(...)` será ignorada. | |||
|
|||
##MockSerializationResult | |||
|
|||
Muito semelhante ao `MockResult` com a diferença que podemos obter o conteúdo serializado no `Result`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd just improve the context here, using something like: "De forma bastante
semelhante, você pode utilizar o MockSerializationResult
sempre que
quiser inspecionar o conteúdo serializado no Result
" What do you think?
@@ -94,6 +94,42 @@ | |||
|
|||
Note that any call of the type `result.use(...)` will be ignored. | |||
|
|||
##MockSerializationResult | |||
|
|||
Very similar to `MockResult` with a difference that we can get the serialized content from `Result`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the same here: "in a similar way, you can use the MockSerializationResult
anytime you want to inspect the serialized content in Result
" (or something)
Besides the minor I've mentioned, it looks good to 🚀. |
Done. |
Adding docs about MockSerializationResult.
merged! thanks again @renanigt |
In the last days, some people asked on Google Groups about how to test a Controller method that just serialize an object.
So, I wrote this little doc about
MockSerializationResult
.