vendredi 5 février 2021

How to prevent Rails 6.1.1 Test from printing entire stack trace errors

image of terminal

E

Error:
PeopleControllerTest#test_should_destroy_person:
ActiveRecord::RecordNotUnique: RuntimeError: UNIQUE constraint failed: users.email
    /Users/n/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:305:in `exec_batch'
    /Users/n/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:305:in `execute_batch2'
    /Users/n/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/activerecord-6.1.1/lib/active_record/connection_adapters/sqlite3/database_statements.rb:122:in `block (2 levels) in execute_batch'
    /Users/n/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/activesupport-
    /Users/n/.rbenv/vers

When I run rails test, each test shows a large wall of errors within the gems. How to only log the relevant info in the console without the entire stack trace.

Aucun commentaire:

Enregistrer un commentaire