From 53cdc729030fa9ed3b1332aeb2bcd0203d8bdc5a Mon Sep 17 00:00:00 2001 From: Pedro Moreira Date: Thu, 4 Jun 2015 10:38:35 +0100 Subject: [PATCH] Do not rely on current public error message 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. --- features/allow_rescue.feature | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/features/allow_rescue.feature b/features/allow_rescue.feature index 94aa93fe..57c01b7d 100644 --- a/features/allow_rescue.feature +++ b/features/allow_rescue.feature @@ -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`