我是Ruby on Rails新手和編寫測試。其中一些產生了例外;我想「耙測試」輸出給我的異常錯誤消息,但不是整個回溯。 (我想寫一個鍛鍊未實現的功能,我將然後填寫測試)Rails測試錯誤時抑制堆棧跟蹤
例如,實際輸出:
Started
E
Finished in 0.081054 seconds.
1) Error:
test_should_fail(VersioningTest):
ActiveRecord::StatementInvalid: PGError: ERROR: null value in column "client_ip" violates not-null constraint
: INSERT INTO "revisions" ("created_at", "id") VALUES ('2011-02-03 20:14:17', 980190962)
/Users/rpriedhorsky/.rvm/gems/ruby-1.9.2-p136/gems/activerecord-3.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:202:in `rescue in log'
/Users/rpriedhorsky/.rvm/gems/ruby-1.9.2-p136/gems/activerecord-3.0.3/lib/active_record/connection_adapters/abstract_adapter.rb:194:in `log'
/Users/rpriedhorsky/.rvm/gems/ruby-1.9.2-p136/gems/activerecord-3.0.3/lib/active_record/connection_adapters/postgresql_adapter.rb:496:in `execute'
[... etc. etc. etc. ...]
1 tests, 0 assertions, 0 failures, 1 errors, 0 skips
所需的輸出:
Started
E
Finished in 0.081054 seconds.
1) Error:
test_should_fail(VersioningTest):
ActiveRecord::StatementInvalid: PGError: ERROR: null value in column "client_ip" violates not-null constraint
1 tests, 0 assertions, 0 failures, 1 errors, 0 skips
我在相反的方向找到信息(e.g.),但不能抑制堆棧軌跡。
編輯:
這將是很好的上下車輕鬆地把他們。正如下面所指出的,有時它們對追蹤錯誤很有用。
好吧,所以事實證明堆棧跟蹤來自文本夾具中的不良數據;隨着修復,產量如我所料。處理基於錯誤假設的問題的禮儀是什麼? – Reid 2011-02-04 15:30:45