forked from rubygems/rubygems.org
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Nick Quaranto <nick@quaran.to>
- Loading branch information
Showing
4 changed files
with
17 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
Feature: Yank Listing | ||
|
||
Scenario: Yanked gem is hidden from listing | ||
Given I am signed up and confirmed as "email@person.com/password" | ||
And I have a gem "RGem" with version "1.2.2" | ||
And I have a gem "RGem" with version "1.2.3" | ||
And I have an api key for "email@person.com/password" | ||
And I've already pushed the gem "RGem-1.2.2.gem" with my api key | ||
And the gem "RGem" with version "1.2.2" has been indexed | ||
And I've already pushed the gem "RGem-1.2.3.gem" with my api key | ||
And the gem "RGem" with version "1.2.3" has been indexed | ||
When I yank the gem "RGem" version "1.2.3" with my api key | ||
And I go to the dashboard | ||
And I follow "RGem" | ||
Then I should not see "yanked" |
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters