sodapopcan
Perhaps oddly, this is the first time I’ve hit this situation in Elixir: I would like to test that a function has only been called once. My use-case is that I’m writing a wrapper around Ecto’s preload and I want to test that when given a list of structs, the implementation looks something like this:
def my_wrapper(structs, preloads) do
MyApp.Repo.preload(structs, preloads)
end
and not this:
def my_wrapper(structs, preloads) do
for struct <- struct do
MyApp.Repo.preload(struct, preloads)
end
end
My only idea so far is to create a mock for MyApp.Repo.preload (which is generally considered a no-no) and have it update a count stored in a gen_server every time it’s called. This is certainly a solution, but does anyone have any better ideas? I have looked at the tests for preload itself and did not come away with anything (although perhaps I didn’t look hard enough?)
Asking here before I resort to asking the robots.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
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
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
jhogberg
trace — OTP 29.0.2 (kernel 11.0.2) ought to do it, just trace it from your test case and make sure you get exactly one message saying it’s been called.
jstimps
Hi, I do this exactly in one of my projects with the trace module! The approach has been a huge help across multiple refactors, to keep performance solid. I love it so much that I wrote a blog post about it.
Asd
Its can be done in a very ergonomic way with Repatch
First, initialize Repatch in
test/test_helper.exsSecond, in test do something like
sodapopcan
I had a very “duh me” moment last night as I was falling asleep when I realized I asked this question while following along in in almost real time with this thread which mentions Repatch for spying.
That’s a great write-up @jstimps, thanks! I really need to start dipping into Erlang libs as these are things I’m aware of but never think to use.
I’m giving @Asd the check as even though it means adding a dependency, I’ve been meaning to give Repatch a try since it was announced and that API is so nice.
Thanks for the answers, all!