cristian.riano
Among many of the tests in our codebase there is a setup repeated multiple times, which is basically starting some required processes (mainly Registries) and looks something like this:
setup do
start_supervised(MyApp.MyModule.Supervisor)
start_supervised({Registry, keys: :unique, name: MyApp.Registry.ById})
...
:ok
end
I want to extract this in a common module so it can be used easier.
My idea was something like this:
- Create a module with setup functions under
test/support - Import the module on the required test
- Call them with in the test setup like
setup :set_my_registries(like defined here
The problem is that the start_supervised function is of course not defined in my module.
My questions are:
- Can I import/require something from ExUnit to make it work?
- Should I try to hack it using Macros and
useit in the test? - Is there a better approach?
PS: I know the philosophy in Elixir tests is to be descriptive but is very annoying when something change names or now there is another dependency and added in all the setup blocks
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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










Showing Posts 4 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
cristian.riano
So for anyone having a similar issue you can import
ExUnit.Callbacksand it should do the trick.My support module (
test/support/my_app_mock.ex) now looks something like thisAnd then it can be used like
Just don’t forget to add the path to the compilation path list (example here)
drl123
Can you just define a special case template like conn_case, data_case, etc. that is
YourApp.RegistryCaseand put that common code in the setup or using block? That way the tests that need it justuse YourApp.RegistryCaseand those that don’t use the usual ones.jswny
Let me know if you figure out a good solution to this, I’m encountering the same exact problem right now where I need to start a bunch of things for each test in the setup block.
LostKobrakai
That should work.