Nuke the chrome feature, since it's disabled for now, long live FF
This commit is contained in:
parent
7e6c2ae352
commit
85bfa1e64d
|
@ -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!
|
Loading…
Reference in New Issue