faux VS wiremock-rs

Faux allows you to create mock versions of a struct without complicating your code. Like many mocking libraries, faux is only recommended for testing purposes. Mock objects in production may be unstable and cause production problems.

I am not a fan of the: "make a trait for every struct so it can be tested" strategy that a lot of mocking libraries or hand rolled mocks do in Rust so I wrote my own library that allows you mock structs directly: https://github.com/nrxus/faux/. Unlike libraries that rely on using traits/dynamic dispatch for mocking this let's your signatures stay as simple as you want them and not incur any runtime cost when doing non-test builds.

for a quick shill moment: I did write a mocking library that deliberately does not pollute the original object and tries to be as out of the way as possible: https://github.com/nrxus/faux/. It does work by using macros (don't hate me yet!) but these macros will only be executed when building for test thus not polluting the original objects for production code.

These are the tests for an example: https://github.com/nrxus/faux/blob/master/tests/asynchronous.rs

Wiremock provides mocking services for applications that interact with HTTP APIs. With Wiremock, you can create mock HTTP servers for testing.

A few weeks ago I was another victim of the RIIR (Rewrite It In Rust) agenda. I got inspired by the awesome wiremock-rs. At first sight, I saw it hadn't the ability to start a mock server from json stubs. That's the kind of functionality I'm intensively using in my daily job of Java developer ; may it be for contract testing with Spring Cloud Contract or for mocking external services in integration (sometimes perf) tests.