Skip to content

Commit

Permalink
Do not rely on current public error message
Browse files Browse the repository at this point in the history
There are slight changes in the error message displayed in the public
error pages across Rails versions. Checking for "We're sorry, but
something went wrong." seems to be the safest option.
  • Loading branch information
pedrosmmoreira committed Jun 4, 2015
1 parent 75ed39d commit 53cdc72
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions features/allow_rescue.feature
Expand Up @@ -32,8 +32,7 @@ Feature: Allow Cucumber to rescue exceptions
visit '/posts'
end
Then /^I should see the public error page$/ do
expect(page).to have_content "We're sorry, but something went wrong. \
If you are the application owner check the logs for more information."
expect(page).to have_content "We're sorry, but something went wrong."
end
"""
And I run `bundle exec rake db:migrate`
Expand Down

0 comments on commit 53cdc72

Please sign in to comment.