Capybara: exception trace in log

Question

While running integration tests in capybara, having app raise an exception (500 error; is rendered in browser) there's no stack trace in test.log file. Here's the only line I see there:

Completed 500 Internal Server Error in 25ms

Am I missing something? How do I make stacktraces appear in test.log during integration testing?

score 46 · Accepted Answer · answered Apr 11 '12 at 15:07

46

Go examine your config/environments/test.rb to find the line:

config.action_dispatch.show_exceptions = false

And change it to true.

answered Apr 11 '12 at 15:07

oldhomemovie

14,621
13
64
99

2

Unfortunately this didn't work for me, but the solution of using mongrel reported here did: http://stackoverflow.com/questions/4627928/get-rails-exceptions-to-show-using-capybara-and-selenium – mmrobins May 10 '12 at 05:46
config.action_dispatch.show_exceptions = true by default on both test and development env! It is not working for me. – Paul Brit Sep 05 '12 at 09:53
1

You changed my life today. Thank you. – Brian Armstrong Oct 23 '12 at 23:47
This sounds like its for Rails >= 3. Anything for Rails 2? – Alex V Oct 08 '13 at 23:05

score 0 · Answer 2 · answered Dec 25 '18 at 18:09

0

The selected answer did not work for me. I'm using Cucumber + Capybara + Rails.

This related answer helped me get the culprit error in the test.log file after running the Cucumber scenario.

answered Dec 25 '18 at 18:09

juliangonzalez

4,231
2
37
47

Capybara: exception trace in log

2 Answers2

Linked