@OvermindDL1
I presume you use Mox.stub_with/2, though, as that’s async, and twiddling Application.put_env is not concurrency-safe.
ityonemo
0
OvermindDL1
No Mox, and I don’t mess with the environment for module names at run-time, I set them in the configuration files. If I want a module to be changed at runtime then I allow it to be passed in the options of individual calls instead. I have a whole delegation pattern I use for this. 
0
ityonemo
Ah yes, am I wrong that this is the pattern that Jose wanted us to use and then everyone was uncomfortable passing modules so Mox was created.
0
LostKobrakai
Not really. Mox handles the mocking part. How you make the mock used by your code is up to you to decide and as you said the app env is not safe for concurrent tests, while passing those into calls as parameter works.
1
ityonemo
No, I was asking if the system being used is this one: “In fact, passing the dependency as argument is much simpler and should be preferred over relying on configuration files and Application.get_env/3” from the original mocks article: Mocks and explicit contracts « Plataformatec Blog that came out before Mox.
1
lccezinha
thiagomajesk
I’ve been using this lib in some projects: GitHub - parroty/exvcr: HTTP request/response recording library for elixir, inspired by VCR. · GitHub. It makes it really easy to test against real scenarios by processing real responses/ payloads.
1