From 85bfa1e64d26d9893f0502677ce8c29eb0d20ee2 Mon Sep 17 00:00:00 2001 From: "R. Tyler Croy" Date: Sun, 9 Dec 2012 22:37:38 -0800 Subject: [PATCH] Nuke the chrome feature, since it's disabled for now, long live FF --- features/cli/{chrome.feature => firefox.feature} | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) rename features/cli/{chrome.feature => firefox.feature} (70%) diff --git a/features/cli/chrome.feature b/features/cli/firefox.feature similarity index 70% rename from features/cli/chrome.feature rename to features/cli/firefox.feature index e32c844..874ce9b 100644 --- a/features/cli/chrome.feature +++ b/features/cli/firefox.feature @@ -1,5 +1,5 @@ -Feature: Start a chrome browser pointing at my Heroku site - In order to test my website in the Chrome browser +Feature: Start a firefox browser pointing at my Heroku site + In order to test my website in the Firefox browser As a Heroku user I should be able to fire up a Sauce Scout instance pointing at my Heroku instance @@ -7,15 +7,15 @@ Feature: Start a chrome browser pointing at my Heroku site Scenario: Without having configured Sauce Given I haven't already configured the plugin - When I run `heroku sauce:chrome` + When I run `heroku sauce:firefox` Then the output should contain: """ Sauce for Heroku has not yet been configured! """ - + @wip Scenario: With Sauce configured Given I have configured the plugin - When I run `heroku sauce:chrome` + When I run `heroku sauce:firefox` Then the output should contain: """ Starting a Chrome session!