newelixiruser
Hi,
I’m trying to test my config settings.
To do that, i use a module that load them: like this
defmodule App.SettingsBehaviour do
@moduledoc """
Define the behavior for accessing environment variable settings
"""
@callback is_search_enabled :: boolean
end
defmodule App.BoundSettings do
@options Application.get_env(:app, :options, App.Settings)
def is_search_enabled do
@options.is_search_enabled
end
end
defmodule App.Settings do
@behaviour App.SettingsBehaviour
@impl App.SettingsBehaviour
def is_search_enabled, do: Application.get_env(:app, :search_enabled, false)
end
config/test.exs
config :app, :options, App.OptionsMock
config :app, search_enabled: true
I have a liveview controller calling App.Settings, and when i try to mock it it returns UnexpectedCallError. Does anyone understand what could fail here?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
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
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
**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 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
cevado
it seems that you have 2 implementations of the module
App.Settings, one doesn’t define the behaviourApp.SettingsBehaviour. one might be overwriting the other.also, are you defining the mock in your test_helper.exs file?
newelixiruser
Sorry, the module name copy was a typo of my part. I corrected it.
Yes i am defining the mocks in supports/mocks.ex!!
cevado
how is your config for
search_enabledin the test config filenewelixiruser
I updated my post with the config/test.exs content
cevado
App.Settingsdoesn’t call any function, just get a value from your Application config store.App.BoundSettingsdoesn’t implement the behaviour.UnexpectedCallErrorusually means that you’re calling the the mock module without setting any expectation on it.given the context you provided, code paths that use
AppBoundSettingsdoesn’t have a expectation onApp.OptionsMock.newelixiruser
One of the expectation was missing making load of tests fails