You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.
By default, Rails in the test environment logs to log/test.log. When I ran bundle exec timber install, it installed a Timber logger that logs to nil. This was confusing the next time I tried to figure out why a test was failing – where did my log go?
In my opinion you should take the same approach in test.rb that you do in development.rb, and emulate standard Rails behavior by logging to log/test.log.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
By default, Rails in the test environment logs to
log/test.log
. When I ranbundle exec timber install
, it installed a Timber logger that logs tonil
. This was confusing the next time I tried to figure out why a test was failing – where did my log go?In my opinion you should take the same approach in
test.rb
that you do indevelopment.rb
, and emulate standard Rails behavior by logging tolog/test.log
.The text was updated successfully, but these errors were encountered: