Update features with new clearance syntax.

rubygems · Sep 14, 2011 · 78a66f6 · 78a66f6
1 parent b25c3c9
commit 78a66f6
Show file tree

Hide file tree

Showing 4 changed files with 17 additions and 17 deletions.
diff --git a/features/homepage.feature b/features/homepage.feature
@@ -1,7 +1,7 @@
 Feature: Homepage
 
   Scenario: Most downloaded gems for today
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And I have a gem "sandworm" with version "1.0.0"
     And I have a gem "sandworm" with version "2.0.0"

diff --git a/features/push.feature b/features/push.feature
@@ -4,7 +4,7 @@ Feature: Push Gems
   Should be able to push gems up to Gemcutter
 
   Scenario: User pushes new gem
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have a gem "RGem" with version "1.2.3"
     And I have an API key for "email@person.com/password"
     When I push the gem "RGem-1.2.3.gem" with my API key
@@ -13,7 +13,7 @@ Feature: Push Gems
     And I should see "1.2.3"
 
   Scenario: User pushes existing version of existing gem
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have a gem "PGem" with version "1.0.0" and summary "First try"
     And I have an API key for "email@person.com/password"
     When I push the gem "PGem-1.0.0.gem" with my API key
@@ -32,7 +32,7 @@ Feature: Push Gems
     And I should see "First try"
 
   Scenario: User pushes new version of existing gem
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And I have a gem "BGem" with version "2.0.0"
     And I push the gem "BGem-2.0.0.gem" with my API key
@@ -44,28 +44,28 @@ Feature: Push Gems
     And I should see "3.0.0"
 
   Scenario: User pushes gem with bad url
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And I have a gem "badurl" with version "1.0.0" and homepage "badurl.com"
     When I push the gem "badurl-1.0.0.gem" with my API key
     Then I should see "Home does not appear to be a valid URL"
 
   Scenario: User pushes gem with bad name
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And I have a bad gem "true" with version "1.0.0"
     When I push the gem "true-1.0.0.gem" with my API key
     Then I should see "Name must be a String"
 
   Scenario: User pushes gem with bad authors
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And I have a gem "badauthors" with version "1.0.0" and authors "[3]"
     When I push the gem "badauthors-1.0.0.gem" with my API key
     Then I should see "Authors must be an Array of Strings"
 
   Scenario: User pushes gem with bad runtime dependency
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And I have a gem "baddeps" with version "1.0.0" and runtime dependency "unknown"
     When I push the gem "baddeps-1.0.0.gem" with my API key
@@ -76,7 +76,7 @@ Feature: Push Gems
   Scenario: User pushes gem with missing :rubygems_version, :specification_version, :name, :version, :date, :summary, :require_paths
 
   Scenario: User pushes file that is not a gem
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     When I push an invalid .gem file
     Then I should see "RubyGems.org cannot process this gem."

diff --git a/features/webhooks.feature b/features/webhooks.feature
@@ -4,7 +4,7 @@ Feature: Web Hooks
   Should be able to configure web hooks to be hit when a gem is pushed
 
   Background:
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
 
   Scenario: User pushes new gem with webhook
     Given I have a gem "fiddler" with version "1.0.0"

diff --git a/features/yank.feature b/features/yank.feature
@@ -4,7 +4,7 @@ Feature: Delete Gems
   I want to delete gems from Gemcutter
 
   Scenario: User yanks a gem
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And the following ownership exists:
       | rubygem    | user                    |
@@ -22,7 +22,7 @@ Feature: Delete Gems
     Then I should see the version "1.2.2" featured
 
   Scenario: User yanks the last version of a gem and a new gem is pushed on that namespace
-    Given I am signed up and confirmed as "email@person.com/password"
+    Given I am signed up as "email@person.com"
     And I have an API key for "email@person.com/password"
     And the following ownership exists:
       | rubygem    | user                    |
@@ -35,7 +35,7 @@ Feature: Delete Gems
     And I follow "RGem"
     Then I should see "This gem has been yanked"
 
-    Given I am signed up and confirmed as "new@owner.com/password"
+    Given I am signed up as "new@owner.com"
     And I have a gem "RGem" with version "0.1.0"
     And I have an API key for "new@owner.com/password"
     When I push the gem "RGem-0.1.0.gem" with my API key
@@ -47,7 +47,7 @@ Feature: Delete Gems
     And I should not see "old@owner.com"
 
   Scenario: User who is not owner attempts to yank a gem
-    Given I am signed up and confirmed as "non@owner.org/password"
+    Given I am signed up as "non@owner.org"
     And I have an API key for "non@owner.org/password"
     And the following version exists:
       | rubygem    | number | indexed |
@@ -59,7 +59,7 @@ Feature: Delete Gems
     Then I should see "You do not have permission to yank this gem."
 
   Scenario: User attempts to yank a nonexistent version of a gem
-    Given I am signed up and confirmed as "the@owner.com/password"
+    Given I am signed up as "the@owner.com"
     And I have an API key for "the@owner.com/password"
     And the following ownership exists:
       | rubygem    | user                 |
@@ -71,7 +71,7 @@ Feature: Delete Gems
     Then I should see "The version 1.2.4 does not exist."
 
   Scenario: User attempts to yank a gem that has already been yanked
-    Given I am signed up and confirmed as "the@owner.com/password"
+    Given I am signed up as "the@owner.com"
     And I have an API key for "the@owner.com/password"
     And the following ownership exists:
       | rubygem    | user                 |
@@ -83,7 +83,7 @@ Feature: Delete Gems
     Then I should see "The version 1.2.3 has already been yanked"
 
   Scenario: User unyanks a gem
-    Given I am signed up and confirmed as "the@owner.com/password"
+    Given I am signed up as "the@owner.com"
     And I have an API key for "the@owner.com/password"
     And the following ownership exists:
       | rubygem    | user                 |