mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
1aa1cec777
This reverts commit224eddfc0e, reversing changes made to9d681fc74c. When merging the pull request, I misunderstood `has_secure_token` as declaring a model has a token from birth and through the rest of its lifetime. Therefore, supporting conditional creation doesn't make sense. You should never mark a model as having a secure token if there's a time when it shouldn't have it on creation.
32 lines
763 B
Ruby
32 lines
763 B
Ruby
require 'cases/helper'
|
|
require 'models/user'
|
|
|
|
class SecureTokenTest < ActiveRecord::TestCase
|
|
setup do
|
|
@user = User.new
|
|
end
|
|
|
|
def test_token_values_are_generated_for_specified_attributes_and_persisted_on_save
|
|
@user.save
|
|
assert_not_nil @user.token
|
|
assert_not_nil @user.auth_token
|
|
end
|
|
|
|
def test_regenerating_the_secure_token
|
|
@user.save
|
|
old_token = @user.token
|
|
old_auth_token = @user.auth_token
|
|
@user.regenerate_token
|
|
@user.regenerate_auth_token
|
|
|
|
assert_not_equal @user.token, old_token
|
|
assert_not_equal @user.auth_token, old_auth_token
|
|
end
|
|
|
|
def test_token_value_not_overwritten_when_present
|
|
@user.token = "custom-secure-token"
|
|
@user.save
|
|
|
|
assert_equal @user.token, "custom-secure-token"
|
|
end
|
|
end
|