Fl4m3Ph03n1x
Background
I have a test file with several describe blocks, each one with a custom setup block, 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 true
end
test "test 2" do
assert true
end
end
# describe group2 ....
end
Here I am setting up a persistent term that I will use along the app. Now, once I reach the end of all tests in the describe block, I want to clean up, meaning I want to delete the "hello" entry from :persistent_term.
To achieve this I am aware of on_exit, but according to my understanding, this callback is only executed once at the end of all tests from all describe blocks.
Questions
- Is my understanding of
on_exitcorrect? - How can I run a clean up function after the tests of each
describeblock?
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
- #api
- #forms
- #elixirconf-eu
- #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.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
idi527
on_exitin asetupblock is executed after each test, in my experience. I’ve never tried usingon_exitinsetup_allthough.Fl4m3Ph03n1x
According to my understanding and in my specific example,
setupwill only be executed once perdescribeblock. What I am looking for is aon_exitthat is executed once per describe block as well.josevalim
setupis always executed per test andon_exitwill always respect the context it is called in. On exit in setup runs after the test. On setup all, after all tests, etc.Fl4m3Ph03n1x
Ahh, so in my example, I am actually running
:persistent_term.put("hello", :world)each time I run a test, and not once per describe block, right?Will the current code run
:persistent_term.put("hello", :world)once per each test inside the givendescribeblock, or once per each test independently?josevalim
It will run once for each test in the describe block. But since it is a side-effect, it will be leaked to other tests.
Fl4m3Ph03n1x
I see. This open an interesting discussion (for another post).
Last set of questions:
setup_allinside adescribeblock, it will ignore it, correct? (meaning it will run as if it wasn’t inside a block, before all tests in the file)on_exitwith setup all? Could someone give me an example? (I have trouble understanding the docs)peerreynders
If I understand the source correctly it won’t even compile.
i.e. it doesn’t look like it is any different from using
on_exit/1inside a regularsetupblock.on_exitregisters a function to perform the teardown (and if the function is created inside the block is has access to anything inside of the block).