Fl4m3Ph03n1x
Background
I have a module that uses eralngs persistent_term. I have some tests that try to use this module and a test file that looks like the following:
defmodule MyAppTest do
use ExUnit.Case
describe "group 1" do
setup do
:persistent_term.put("hello", :world)
:ok
end
test "test 1" do
assert MyApp.run(:random_data)
end
end
# describe group2 ....
end
Problem
Here the code in the setup block will run before each test inside the describe block. However, since persistent_term is a side effect, this will leak to other tests. MyApp.run/1 uses :persistent_term, so it means that MyApp.run/1 has side effects.
Question
How do you test functions with side effects in Elixir?
How would you test MyApp.run/1 without leaking the test data into other tests?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
ElixirConf EU 2027, 22-23 April, Lisbon & online. Call for Talks and Call for Training open until 15 Dec.
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #elixirconf-us
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance
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. Next: ElixirConf EU 2027
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**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 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
This is probably the only answer for this…
But anyway, you are not testing the sideeffect, but you are testing your function under a certain environment. Slightly different…
Anyway, I still think that running them with
async: falseand properly cleaning up is your only option…svarlet
Are you testing configuration instead of some code?
NobbZ
It tests behaviour under a certain configuration if you want to say so…
And yes, sometimes I do so…
Anyway, under “testing sideeffects” I’d actually understand, to test if a file exists and has a given content after calling
File.write.Fl4m3Ph03n1x
iirc,
async: falsedoes not mean my tests will run synchronously between each other, it means that each test file will run 1 at a time, instead of running all test files at the same time.So it is unclear to me how this would be a solution to the issue at hand.
Am I incorrect?
I’m testing code. The module at hand has functions that save data to :persistent_term. I want to make sure that data is being saved correctly.
idi527
Tests within a single test file always run after one another, never at the same time. You can update your setup block to clean the persistent term storage and then insert “hello”. This way all test block would start with known state.