crisefd
Managing different test environments with mix aliases
Hi. My project has both unit and property tests. Unit tests are using a mocking library but I don’t need my property tests to run with the mocks, so I decided to split my test env into two: test and property_test using test.exs and property_test.exs config files respectively. Finally, I’m running these tests using the commands:
$ MIX_ENV=property_test mix test test/property/
$ MIX_ENV=test mix test test/unit
Now, I would like to instead create custom commands to simplify things using Mix’s aliases but I don’t know how to achieve it. Like how would that look like ? I don’t know how to tell Mix which env it should execute each alias with. This is what I have so far in my mix.exs
def cli do
[preferred_envs: ["test.unit": :test, "test.property": :property_test]]
end
defp aliases() do
[
"test.property": ["test test/property/"],
"test.unit": ["test test/unit"]
]
end
But I’m still getting this error
** (Mix) “mix test” is running in the “property_test” environment. If you are running tests from within another command, you can either:
set MIX_ENV explicitly:
MIX_ENV=test mix test.another
set the :preferred_envs for “def cli” in your mix.exs:
def cli do
[preferred_envs: [“test.another”: :test]]
end
Trending in Questions
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security










Marked As Solved
crisefd
Ok, so I actually don’t know why this approach fails, but I managed to make it work with this hack in the aliases definition (everything else needs to stay the same).
Forciby setting the
MIX_ENVvariable plus setting the preferred envs in theclifunction does it. This seems like a bug to me, I’m using Elixir 1.16.0 if it helps anyone else.Last Post!
dimitarvp
Sure, my point was that just for one or more tests you can skip the
external_api()mediator and use the real thing instead.