slouchpie
ExUnit wish - retrospective `:test` env logger level
In :test env I have the usual logger config 
# Print only warnings and errors during test
config :logger, level: :warning
which means I have a nice clean console if everything passes (and I use capture_log and with_log when necessary).
Something I would very much enjoy is if I could somehow get the :info logs for failed tests only.
It has to be possible, right? Maybe some kind of custom logger that holds the :info logs in memory and only prints them if current test fails?
If it is possible, it would be really nice to be able to write logger config like this:
My wish
config :logger, level: [passed: :warning, failed: :info]
Trending in Discussions
Other Trending Topics
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
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
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First Post!
arcanemachine
Here’s how I have my
config/test.exsset up:Using this, you could run
mix testto get the standard warning/error logs, then you could runLOG_LEVEL=info mix test --failedto get more detailed logs for your failed tests (could also use--traceto make it easier to tell which logs apply to which tests, perhaps).It’s not quite what you’re asking for, but could get you something close to the desired results with very little work involved.
Most Liked
LostKobrakai
I usually put a
Logger.configure(level: level)in the test in question.slouchpie
These are useful and good techniques.
However, my wish is for a 0-effort solution that will also catch, say, a “flakey” test that fails sometimes and only when run as part of an entire async test suite. I do not want to have to manually change the log level and re-run tests. I want…magic!
LostKobrakai
You could generally enable logs and use ExUnit.Case — ExUnit v1.20.2 to show them only in case of errors.
There is however no magic after the fact getting access to already dropped logs.
Last Post!
garrison
Only marginally on topic here but this is one of the beautiful things about tests which are completely deterministic. When designed correctly you can retroactively re-enable (sometimes expensive) logging without changing the result. Obviously this is difficult to implement in practice, and not always possible