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

Answer 1

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.