wiremock-rs icon indicating copy to clipboard operation
wiremock-rs copied to clipboard

HTTP mocking to test Rust applications.

Results 21 wiremock-rs issues
Sort by recently updated
recently updated
newest added

Right now, if a `MockServer` receives an unexpected call then this gets logged and an `HTTP 404` is returned to the client. It would be useful if there was some...

Hey, as in issue title. I wanted to test that a service gracefully handles networking issues like server being temporarily unreachable and wanted to do that by dropping the `MockServer`,...

Seems that the features is enabled by hyper_util but it's not enabled on this crate even though it's being used. I was exploring the option to make wiremock wasm-unknown-unknown happy...

Sometimes it'd be useful to have some logic run after a mock finished responding (so the client doing the request received the response). Currently this doesn't seem to be possible....

*Description of changes:* Request bodies can be encoded as form https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST Add an helper function to decode those bodies easily. By submitting this pull request, I confirm that you can...

*Description of changes:* Add support to _streaming body_, hopefully without any breaking change (according to [cargo-semver-checks](https://github.com/obi1kenobi/cargo-semver-checks), there aren't). The rationale is that it is useful to simulate delays or errors...

Follow-up from #125: it might be nice to give users the possibility to store the requests received by the mock server to disk, either because they are not printed (too...

In the documentation for [wiremock.org](https://wiremock.org/docs/stubbing/) is a folder with JSON files that can be used to configure the stubs and matches. Is there any chance this will be supported here...

Thanks for wiremock! It seems that it's currently not possible to execute async code in the respond method or respond trait. It'd be useful to have it natively supported by...

The entire request being printed out when the body is exceptional large or contains binary data leads to poor debugging when a guard fails. I could provide a real example...