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.
Merge pull request rubygems#350 from rubygems/update_clearance
Update clearance.
- Loading branch information
Showing
71 changed files
with
447 additions
and
518 deletions.
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
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,14 @@ | ||
# A sample Guardfile | ||
# More info at https://github.com/guard/guard#readme | ||
|
||
guard 'cucumber' do | ||
watch(%r{^features/.+\.feature$}) | ||
watch(%r{^features/support/.+$}) { 'features' } | ||
watch(%r{^features/step_definitions/(.+)_steps\.rb$}) { |m| Dir[File.join("**/#{m[1]}.feature")][0] || 'features' } | ||
end | ||
|
||
guard 'bundler' do | ||
watch('Gemfile') | ||
# Uncomment next line if Gemfile contain `gemspec' command | ||
# watch(/^.+\.gemspec/) | ||
end |
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
This file was deleted.
Oops, something went wrong.
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
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 |
---|---|---|
@@ -1,14 +1,6 @@ | ||
Welcome to RubyGems.org, the Ruby community's gem hosting service! | ||
|
||
To confirm your account, please follow this link: | ||
|
||
<%= new_user_confirmation_url( | ||
:user_id => @user, | ||
:token => @user.confirmation_token, | ||
:encode => false) %> | ||
|
||
If you're having trouble getting set up, let us know at: | ||
|
||
http://help.rubygems.org | ||
|
||
Happy gem push'ing! |
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 |
---|---|---|
@@ -1,3 +0,0 @@ | ||
You changed your email address on Gemcutter. Please visit this url to re-activate your account: | ||
|
||
<%= new_user_confirmation_url :user_id => @user, :token => @user.confirmation_token, :encode => false %> | ||
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
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
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
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
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,53 @@ | ||
Feature: Password reset | ||
|
||
In order to sign in even if I forgot my password | ||
As a user | ||
I want to reset my password | ||
|
||
Scenario: User is not signed up | ||
Given no user exists with an email of "email@example.com" | ||
When I request password reset link to be sent to "email@example.com" | ||
Then I should see "Unknown email" | ||
|
||
Scenario: User is signed up and requests password reset | ||
Given I signed up with "email@example.com" | ||
When I request password reset link to be sent to "email@example.com" | ||
Then I should see "instructions for changing your password" | ||
And a password reset message should be sent to "email@example.com" | ||
|
||
Scenario: User tries to reset his password with a blank password | ||
Given I signed up with "email@example.com" | ||
And I go to the password reset request page | ||
Then I should see an email field | ||
And I fill in "Email address" with "email@example.com" | ||
And I press "Reset password" | ||
When I follow the password reset link sent to "email@example.com" | ||
And I update my password with "" | ||
Then I should see "Password can't be blank." | ||
And I should be signed out | ||
|
||
Scenario: User is signed up and updates his password | ||
Given I signed up with "email@example.com" | ||
And I go to the password reset request page | ||
And I fill in "Email address" with "email@example.com" | ||
And I press "Reset password" | ||
When I follow the password reset link sent to "email@example.com" | ||
And I update my password with "newpassword" | ||
Then I should be signed in | ||
When I sign out | ||
Then I should be signed out | ||
When I go to the sign in page | ||
And I fill in "Email" with "email@example.com" | ||
And I fill in "Password" with "newpassword" | ||
And I press "Sign in" | ||
Then I should be signed in | ||
|
||
Scenario: User who was created before Clearance was installed creates password for first time | ||
Given a user "email@example.com" exists without a salt, remember token, or password | ||
When I go to the password reset request page | ||
And I fill in "Email address" with "email@example.com" | ||
And I press "Reset password" | ||
When I follow the password reset link sent to "email@example.com" | ||
And I update my password with "newpassword" | ||
Then I should be signed in | ||
|
Oops, something went wrong.