This post was originally published on the Elixir School blog. Elixir School is an open source Elixir curriculum and we're looking for contributors! You can write a short TIL blog post, a longer blog post, add a lesson, help with translation and more. Check out our open issues or add one of your own here
If you're working on an Elixir umbrella app with multiple children, then you know that running the tests for the entire umbrella app isn't always ideal. It could take a while to run and it can be hard to zero in on one particular set of failures when deving on just of the child apps.
So, how can you run tests for just one specific child app?
Not Like This
My first attempt to run just one child app's tests went a little something like this:
mix test test/github_client_test.exs ==> learn_client Paths given to `mix test` did not match any directory/file: test/github_client_test.exs ==> course_suite_client Paths given to `mix test` did not match any directory/file: test/github_client_test.exs ==> github_client .... Finished in 0.2 seconds 4 tests, 0 failures Randomized with seed 395181 ==> deployer Paths given to `mix test` did not match any directory/file: test/github_client_test.exs ==> deployer_web Paths given to `mix test` did not match any directory/file: test/github_client_test.exs
This technically works--it did run the test we specified--but its not quite what we want. Any
mix command we run from the root of our umbrella app is recursively run from the root of each child app in the
apps/ directory. So, while this did run the
github_client_test.exs test when the command was executed in the child app that contains that test, it also executed that command against every other child app. Resulting in these not-so-nice error messages:
Paths given to `mix test` did not match any directory/file: test/github_client_test.exs
To run all of the tests for just one specific child app, we can run the following from the root of the umbrella app:
mix cmd --app child_app_name mix test --color
mix cmd --app to indicate the app within which we want to run a given
mix command. We follow that with the
mix test command. Additionally, we can specify a test file and even line number to run:
mix cmd --app child_app_name mix test test/child_app_name_test.exs:8 --color
mix test command is followed by the path to the test file you want to run, from the root of that child app.
--color flag is important. Without it, we don't get that nice red/green color highlighting, leaving our test output pretty hard to read.
Typing this command every time we want to run a given child app's tests is kind of a pain. We can define a mix alias to make our lives a little easier. A mix alias provides us a way to define a custom mix task that will only be available locally, not in packaged versions of our application, i.e. not to devs who install our app as a dependency.
We'll define a mix alias for our child app test command:
# mix.exs for root of umbrella app def project do [ aliases: aliases(), ... ] end def aliases do [ child_app_name_test: "cmd --app child_app_name mix test --color" ] end
Then from the root of umbrella app, we can run:
Or, to run a specific test:
mix child_app_name_test test/child_app_name_test.exs
And that's it! A nice, easy-to-use command for running a child app's specs. You could define one such alias for each child app in your umbrella and run those tests with ease.