Using Logger.info and Logger.debug in ExUnit tests
Subscribe to receive Elixir news to your inbox every two weeks.
Expand your skills
Download free e-books, watch expert tech talks, and explore open-source projects. Everything you need to grow as a developer - completely free.
By default in the test env, Phoenix doesn't show Logger.debug/Logger.info outputs in the console.
Logger provides 4 printing levels:
- info (allows errors, warns, debugs, infos)
- debug (allows errors, warns, debugs)
- warn (allows errors, warns)
- error (allows errors)
By default the :warn level is turned on. It means that only Logger.warn and Logger.error is printed to the output.
If you'd like to use another two, go to your config/test.exs file and you'll probably see:
# Print only warnings and errors during test
config :logger, level: :warnJust change the line to the proper level (:debug or :info), and you're ready to go:
# Print all (errors, warnings, debugs and infos) during tests
config :logger, level: :infoWork with a team that keeps learning and building better software every day.
Related posts
Dive deeper into this topic with these related posts
You might also like
Discover more content from this category
Warnings in Elixir are usually an important sign of a problem in the codebase. There is an easy way to make them gone.
So you don’t know what’s the type of struct you’re passing somewhere? Maybe it can be one of few types and you have to distinguish them? Or any other reason… But it’s about checking the struct type. Just use one of the coolest Elixir features - pattern matching!
There are a bunch of operations you may want to perform before the rendered response in conn is sent to the client, such as minification. In this post I'll show you how to do it easily.