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
Nowadays, with an ever-growing number of web services, we tend to overload Web apps with external resources. As a result, it decreases page load speed and affects SEO score. There is a pretty easy solution for that.
In some cases, like for testing purposes, you might want to use an npm package stored on a local machine. Here is how you can do that with one simple command.
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.