Fl4m3Ph03n1x
Background
I have a considerable test suite for my app with unit tests and integrated tests. The application has a considerable size so it has quite a number of Logger.debug, Logger.info and Logger.error calls spread around everywhere.
Objective
This means that when I run mix test my output gets polluted with hundreds of lines of logs. I need these logs so removing them from production code is not really an option, but I would like to hide them when testing.
Problem
To achieve this I changed my test_helper.exs to have the following content:
ExUnit.start(capture_log: true)
However when I run mix test I see a ton of l debug and even info logs.
Questions
How can I hide all logs from showing when running mix test ?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
jola
The test config (
config/test.exs) generated bymix phx.newhas this.Fl4m3Ph03n1x
I don’t even want those because since I am (also) testing for errors the
Logger.errorcalls will still pollute my output. I am pickyjola
config :logger, backends: []will disable logging. You can find all the options here Logger — Logger v1.20.2rodrigues
for other kinds of outputs,
capture_io/1might help cleanup test output: ExUnit.CaptureIO — ExUnit v1.20.2sasajuric
When testing for errors, you can use ExUnit.CaptureLog to capture log messages (which then won’t appear in the output).
In general, I wouldn’t advise muting errors in tests, since they might be indicative of why some tests are failing.
Fl4m3Ph03n1x
This is … a good point. I have changed my config to the following:
As @jola suggested. This should do it, even though I may see some logs I don’t want to, I think the compromise is fair.
hackvan
You can use only in the test that triggers Log output the
@moduletagdirective: