I have a GenSever that hits an external API every 5 secs. Because of the limited number of API requests, I’m using Docker to run the app locally. Now even when running tests and even using Mimic library , I need to have Docker API instance running. I have several questions regarding how to avoid s…

By default only files in lib/ are compiled. Test files are scripts and called by the test runner. However in mix.exs you can add additional folders for source files to be compiled. Many elixir projects configure test/support to be such a folder for the test mix env: Add Elixir files to your compiled…

[image] LostKobrakai: There’s also no need to configure things at compile time. Mox doesn’t care how you switch out implementations, only that you do so. Isn’t that distinction strictly academical? I mean OK, I find the following worse: GithubClient.impl().get_forks(username) …than this: G…

[image] dimitarvp: BTW I am really curious if you can offer other patterns for having an implementation vary depending on Mix.env – any others except the two I mentioned? Admittedly I haven’t shopped around for such practices in a long time so might be one of my blind spots. I think we got th…

[image] LostKobrakai: Without that I wouldn’t trust myself debugging a failing test a few month down the line and being able to figure out if the code is wrong or the mock implementation is wrong. You can have and use a @behaviour even if you don’t use mox. :person_shrugging: And I agree that…

[image] dimitarvp: Would you say you don’t find it as annoying as I do? That. I tend to put selections behind impl functions in some places, but more recently I tend to prefer passing those implementations around top to bottom. I guess all OTP behaviours work like that as well. You never call…

[image] LostKobrakai: You never call MyGenServer.handle_info either and :gen_server just passes around a variable for the module being the behaviour implementation. Hmmm okay, I can see that, though in the case of GenServer we’re talking about a “live” entity – a separate process – and in our…

[image] dimitarvp: Hmmm okay, I can see that, though in the case of GenServer we’re talking about a “live” entity – a separate process – and in our case we’re talking about a “dead” module that has to invoke the network when its functions are called. Nothing on the beam runs outside a process…

[image] dimitarvp: Well OK, it’s hard to disagree on this but how do you cope with the visual noise? I basically don’t see it. My regular code just calls (as an example) FlightTracker.get_flights(tracking_number). That module both defines the behavior but also does def get_flights(number) do…

[image] benwilson512: That module both defines the behavior but also does … This is what I eventually settled on as well but it feels very… unclean. Both a behaviour module and an implementation dispatcher. Two in one. But I am the first guy around here to make a huge stink about having too …

I try to avoid introducing behaviour if this is only for test. If the behaviour already exists because the production code uses different implementations, then Mox all the way, but otherwise no. If the code calls an external thing such as an HTTP API we mock that with a real HTTP server. Even if it …

Wow, I provoked a huge wave of discussions, some of them are still beyond of my understanding. Thank you all for bringing your experience and knowledge stones to the base. What confuses me most is that n my simple app, I have a GenServer defies to be started as a child process wen the app starts: #…

Elixir Programming Language Forum

GenServer: avoid refresh running in tests

Questions & Help Questions

belgoros March 31, 2024, 7:15pm 18

Ah, I got it, thanks a lot!