fireproofsocks
I have a couple Elixir modules that rely in part on 3rd party APIs. I’m wondering how I can best test them? Since the 3rd party service may be down or we may experience time-outs or we may have mis-configured the connection entirely, it is important that our module can recover and log any problems.
One gotcha is that Elixir reads ENV variables at compile-time. If I wanted to test that the proper URL had been entered, I would have to restructure my module and functions to allow for me to inject an override. Is this recommended?
Another not-so-hypothetical case is that our account with the 3rd party may have lapsed – let’s say our contract expired without anyone noticing. In that case, our API token would stop working and their API would start returning an error page. Again, I could refactor our modules so that I could inject a fake response, but it seems like that approach is not idiomatic to Elixir.
Any suggestions? Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Jose wrote about mocks a while ago: Mocks and explicit contracts.
Long story short, it involves configuring implementations of APIs per environment but mandates you create a behaviour which serves as a contract.
As for 3rd party APIs erroring, I am not sure what your question really is; if the API starts erroring out surely you can catch the
{:error, reason}tuples in your calling functions and react accordingly? Sorry if I misunderstood your problem there.fireproofsocks
Thanks, I’ll look at that article. The point with the 3rd party API is that we don’t know if or when it will throw errors, but in order to test our implementation we need to be able to simulate those responses.
dimitarvp
Then maybe Bypass will be of help. See BleacherReport’s article about it.