clearance 0.9.1 → 0.10.0

data/app/views/clearance_mailer/confirmation.html.erb

@@ -1,5 +0,0 @@
-
-<%= new_user_confirmation_url(
-      :user_id => @user,
-      :token   => @user.confirmation_token,
-      :encode  => false) %>

data/spec/rails_root/db/schema.rb

@@ -1,29 +0,0 @@
-# This file is auto-generated from the current state of the database. Instead
-# of editing this file, please use the migrations feature of Active Record to
-# incrementally modify your database, and then regenerate this schema definition.
-#
-# Note that this schema.rb definition is the authoritative source for your
-# database schema. If you need to create the application database on another
-# system, you should be using db:schema:load, not running all the migrations
-# from scratch. The latter is a flawed and unsustainable approach (the more migrations
-# you'll amass, the slower it'll run and the greater likelihood for issues).
-#
-# It's strongly recommended to check this file into your version control system.
-
-ActiveRecord::Schema.define(:version => 20101220185807) do
-
-  create_table "users", :force => true do |t|
-    t.string   "email"
-    t.string   "encrypted_password", :limit => 128
-    t.string   "salt",               :limit => 128
-    t.string   "confirmation_token", :limit => 128
-    t.string   "remember_token",     :limit => 128
-    t.boolean  "email_confirmed",                   :default => false, :null => false
-    t.datetime "created_at"
-    t.datetime "updated_at"
-  end
-
-  add_index "users", ["email"], :name => "index_users_on_email"
-  add_index "users", ["remember_token"], :name => "index_users_on_remember_token"
-
-end

data/spec/rails_root/features/password_reset.feature

@@ -1,33 +0,0 @@
-Feature: Password reset
-  In order to sign in even if user forgot their password
-  A user
-  Should be able to reset it
-
-    Scenario: User is not signed up
-      Given no user exists with an email of "email@person.com"
-      When I request password reset link to be sent to "email@person.com"
-      Then I should see "Unknown email"
-
-    Scenario: User is signed up and requests password reset
-      Given I signed up with "email@person.com/password"
-      When I request password reset link to be sent to "email@person.com"
-      Then I should see "instructions for changing your password"
-      And a password reset message should be sent to "email@person.com"
-
-    Scenario: User is signed up updated his password and types wrong confirmation
-      Given I signed up with "email@person.com/password"
-      When I follow the password reset link sent to "email@person.com"
-      And I update my password with "newpassword/wrongconfirmation"
-      Then I should see an error message
-      And I should be signed out
-
-    Scenario: User is signed up and updates his password
-      Given I signed up with "email@person.com/password"
-      When I follow the password reset link sent to "email@person.com"
-      And I update my password with "newpassword/newpassword"
-      Then I should be signed in
-      When I sign out
-      Then I should be signed out
-      And I sign in as "email@person.com/newpassword"
-      Then I should be signed in
-

data/spec/rails_root/features/sign_in.feature

@@ -1,35 +0,0 @@
-Feature: Sign in
-  In order to get access to protected sections of the site
-  A user
-  Should be able to sign in
-
-    Scenario: User is not signed up
-      Given no user exists with an email of "email@person.com"
-      When I go to the sign in page
-      And I sign in as "email@person.com/password"
-      Then I should see "Bad email or password"
-      And I should be signed out
-
-    Scenario: User is not confirmed
-      Given I signed up with "email@person.com/password"
-      When I go to the sign in page
-      And I sign in as "email@person.com/password"
-      Then I should see "User has not confirmed email"
-      And I should be signed out
-
-   Scenario: User enters wrong password
-      Given I am signed up and confirmed as "email@person.com/password"
-      When I go to the sign in page
-      And I sign in as "email@person.com/wrongpassword"
-      Then I should see "Bad email or password"
-      And I should be signed out
-
-   Scenario: User signs in successfully
-      Given I am signed up and confirmed as "email@person.com/password"
-      When I go to the sign in page
-      And I sign in as "email@person.com/password"
-      Then I should see "Signed in"
-      And I should be signed in
-      When I return next time
-      Then I should be signed in
-

data/spec/rails_root/features/sign_out.feature

@@ -1,15 +0,0 @@
-Feature: Sign out
-  To protect my account from unauthorized access
-  A signed in user
-  Should be able to sign out
-
-    Scenario: User signs out
-      Given I am signed up and confirmed as "email@person.com/password"
-      When I sign in as "email@person.com/password"
-      Then I should be signed in
-      And I sign out
-      Then I should see "Signed out"
-      And I should be signed out
-      When I return next time
-      Then I should be signed out
-

data/spec/rails_root/features/sign_up.feature

@@ -1,45 +0,0 @@
-Feature: Sign up
-  In order to get access to protected sections of the site
-  A user
-  Should be able to sign up
-
-    Scenario: User signs up with invalid data
-      When I go to the sign up page
-      And I fill in "Email" with "invalidemail"
-      And I fill in "Password" with "password"
-      And I fill in "Confirm password" with ""
-      And I press "Sign up"
-      Then I should see error messages
-
-    Scenario: User signs up with valid data
-      When I go to the sign up page
-      And I fill in "Email" with "email@person.com"
-      And I fill in "Password" with "password"
-      And I fill in "Confirm password" with "password"
-      And I press "Sign up"
-      Then I should see "instructions for confirming"
-      And a confirmation message should be sent to "email@person.com"
-
-    Scenario: User confirms his account
-      Given I signed up with "email@person.com/password"
-      When I follow the confirmation link sent to "email@person.com"
-      Then I should see "Confirmed email and signed in"
-      And I should be signed in
-
-    Scenario: Signed in user clicks confirmation link again
-      Given I signed up with "email@person.com/password"
-      When I follow the confirmation link sent to "email@person.com"
-      Then I should be signed in
-      When I follow the confirmation link sent to "email@person.com"
-      Then I should see "Confirmed email and signed in"
-      And I should be signed in
-
-    Scenario: Signed out user clicks confirmation link again
-      Given I signed up with "email@person.com/password"
-      When I follow the confirmation link sent to "email@person.com"
-      Then I should be signed in
-      When I sign out
-      And I follow the confirmation link sent to "email@person.com"
-      Then I should see "Already confirmed email. Please sign in."
-      And I should be signed out
-

data/spec/rails_root/features/step_definitions/clearance_steps.rb

@@ -1,138 +0,0 @@
-# General
-
-Then /^I should see error messages$/ do
-  Then %{I should see "errors prohibited"}
-end
-
-Then /^I should see an error message$/ do
-  Then %{I should see "error prohibited"}
-end
-
-# Database
-
-Given /^no user exists with an email of "(.*)"$/ do |email|
-  assert_nil User.find_by_email(email)
-end
-
-Given /^I signed up with "(.*)\/(.*)"$/ do |email, password|
-  user = Factory :user,
-    :email                 => email,
-    :password              => password,
-    :password_confirmation => password
-end
-
-Given /^I am signed up and confirmed as "(.*)\/(.*)"$/ do |email, password|
-  user = Factory :email_confirmed_user,
-    :email                 => email,
-    :password              => password,
-    :password_confirmation => password
-end
-
-# Session
-
-Then /^I should be signed in$/ do
-  Given %{I am on the homepage}
-  Then %{I should see "Sign out"}
-end
-
-Then /^I should be signed out$/ do
-  Given %{I am on the homepage}
-  Then %{I should see "Sign in"}
-end
-
-When /^session is cleared$/ do
-  # TODO: This doesn't work with Capybara
-  # TODO: I tried Capybara.reset_sessions! but that didn't work
-  #request.reset_session
-  #controller.instance_variable_set(:@_current_user, nil)
-end
-
-Given /^I have signed in with "(.*)\/(.*)"$/ do |email, password|
-  Given %{I am signed up and confirmed as "#{email}/#{password}"}
-  And %{I sign in as "#{email}/#{password}"}
-end
-
-Given /^I sign in$/ do
-  email = Factory.next(:email)
-  Given %{I have signed in with "#{email}/password"}
-end
-
-# Emails
-
-Then /^a confirmation message should be sent to "(.*)"$/ do |email|
-  user = User.find_by_email(email)
-  assert !user.confirmation_token.blank?
-  assert !ActionMailer::Base.deliveries.empty?
-  result = ActionMailer::Base.deliveries.any? do |email|
-    email.to == [user.email] &&
-    email.subject =~ /confirm/i &&
-    email.body =~ /#{user.confirmation_token}/
-  end
-  assert result
-end
-
-When /^I follow the confirmation link sent to "(.*)"$/ do |email|
-  user = User.find_by_email(email)
-  visit new_user_confirmation_path(:user_id => user,
-                                   :token   => user.confirmation_token)
-end
-
-Then /^a password reset message should be sent to "(.*)"$/ do |email|
-  user = User.find_by_email(email)
-  assert !user.confirmation_token.blank?
-  assert !ActionMailer::Base.deliveries.empty?
-  result = ActionMailer::Base.deliveries.any? do |email|
-    email.to == [user.email] &&
-    email.subject =~ /password/i &&
-    email.body =~ /#{user.confirmation_token}/
-  end
-  assert result
-end
-
-When /^I follow the password reset link sent to "(.*)"$/ do |email|
-  user = User.find_by_email(email)
-  visit edit_user_password_path(:user_id => user,
-                                :token   => user.confirmation_token)
-end
-
-When /^I try to change the password of "(.*)" without token$/ do |email|
-  user = User.find_by_email(email)
-  visit edit_user_password_path(:user_id => user)
-end
-
-Then /^I should be forbidden$/ do
-  assert_response :forbidden
-end
-
-# Actions
-
-When /^I sign in as "(.*)\/(.*)"$/ do |email, password|
-  When %{I go to the sign in page}
-  And %{I fill in "Email" with "#{email}"}
-  And %{I fill in "Password" with "#{password}"}
-  And %{I press "Sign in"}
-end
-
-When "I sign out" do
-  steps %{
-    When I go to the homepage
-    And I follow "Sign out"
-  }
-end
-
-When /^I request password reset link to be sent to "(.*)"$/ do |email|
-  When %{I go to the password reset request page}
-  And %{I fill in "Email address" with "#{email}"}
-  And %{I press "Reset password"}
-end
-
-When /^I update my password with "(.*)\/(.*)"$/ do |password, confirmation|
-  And %{I fill in "Choose password" with "#{password}"}
-  And %{I fill in "Confirm password" with "#{confirmation}"}
-  And %{I press "Save this password"}
-end
-
-When /^I return next time$/ do
-  When %{session is cleared}
-  And %{I go to the homepage}
-end

data/test/controllers/confirmations_controller_test.rb

@@ -1,107 +0,0 @@
-require 'test_helper'
-
-class ConfirmationsControllerTest < ActionController::TestCase
-
-  tests Clearance::ConfirmationsController
-
-  should filter_param(:token)
-
-  context "a user whose email has not been confirmed" do
-    setup { @user = Factory(:user) }
-
-    should "have a token" do
-      assert_not_nil @user.confirmation_token
-      assert_not_equal "", @user.confirmation_token
-    end
-
-    context "on GET to #new with correct id and token" do
-      setup do
-        get :new, :user_id => @user.to_param,
-                  :token   => @user.confirmation_token
-      end
-
-      should set_the_flash.to(/confirmed email/i)
-      should set_the_flash.to(/signed in/i)
-      should_redirect_to_url_after_create
-
-      should "set the current user" do
-        assert_equal @user, @controller.current_user
-      end
-    end
-
-    context "with an incorrect token" do
-      setup do
-        @bad_token = "bad token"
-        assert_not_equal @bad_token, @user.confirmation_token
-      end
-
-      should_forbid "on GET to #new with incorrect token" do
-        get :new, :user_id => @user.to_param,
-                  :token   => @bad_token
-      end
-    end
-
-    should_forbid "on GET to #new with blank token" do
-      get :new, :user_id => @user.to_param, :token => ""
-    end
-
-    should_forbid "on GET to #new with no token" do
-      get :new, :user_id => @user.to_param
-    end
-  end
-
-  context "a signed in confirmed user on GET to #new with token" do
-    setup do
-      @user  = Factory(:user)
-      @token = @user.confirmation_token
-      @user.confirm_email!
-      sign_in_as @user
-
-      get :new, :user_id => @user.to_param, :token => @token
-    end
-
-    should set_the_flash.to(/confirmed email/i)
-    should_redirect_to_url_after_create
-  end
-
-  context "a bad user" do
-    setup do
-      @user  = Factory(:user)
-      @token = @user.confirmation_token
-      @user.confirm_email!
-
-      @bad_user = Factory(:email_confirmed_user)
-      sign_in_as @bad_user
-    end
-
-    should_forbid "on GET to #new with token for another user" do
-      get :new, :user_id => @user.to_param, :token => @token
-    end
-  end
-
-  context "a signed out confirmed user on GET to #new with token" do
-    setup do
-      @user  = Factory(:user)
-      @token = @user.confirmation_token
-      @user.confirm_email!
-      get :new, :user_id => @user.to_param, :token => @token
-    end
-
-    should set_the_flash.to(/already confirmed/i)
-    should set_the_flash.to(/sign in/i)
-    should_redirect_to_url_already_confirmed
-
-    should "not be signed in" do
-      assert_nil cookies[:remember_token]
-    end
-  end
-
-  context "no users" do
-    setup { assert_equal 0, ::User.count }
-
-    should_forbid "on GET to #new with nonexistent id and token" do
-      get :new, :user_id => '123', :token => '123'
-    end
-  end
-
-end