Databases
StackOverflow2013
Postsdbo
PORails 3 tutorial chapter 6 strange Rspec failures
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails 3 tutorial chapter 6 strange Rspec failures
    primarykey
    data
    text
    <p>I'am fighting with Rails tutoril. I've stucked on 6th chapter. Here is the problem When I run test:</p> <pre><code>bundle exec rspec spec/models/user_spec.rb I get few failures: Failures: 1) User ←[31mFailure/Error:←[0m ←[31mit { should be_valid }←[0m ←[31mexpected valid? to return true, got false←[0m ←[36m # ./spec/models/user_spec.rb:31:in `block (2 levels) in &lt;top (required )&gt;'←[0m 2) User when email format is valid should be valid ←[31mFailure/Error:←[0m ←[31m@user.should be_valid←[0m ←[31mexpected valid? to return true, got false←[0m ←[36m # ./spec/models/user_spec.rb:64:in `block (4 levels) in &lt;top (required )&gt;'←[0m ←[36m # ./spec/models/user_spec.rb:62:in `each'←[0m ←[36m # ./spec/models/user_spec.rb:62:in `block (3 levels) in &lt;top (required )&gt;'←[0m 3) User return value of authenticate method with valid password ←[31mFailure/Error:←[0m ←[31mit { should == found_user.authenticate(@user.p assword) }←[0m ←[31mNoMethodError:←[0m ←[31mundefined method `authenticate' for nil:NilClass←[0m ←[36m # ./spec/models/user_spec.rb:99:in `block (4 levels) in &lt;top (required )&gt;'←[0m 4) User return value of authenticate method with invalid password ←[31mFailure/Error:←[0m ←[31mlet(:user_for_invalid_password) { found_user.a authenticate("invalid") }←[0m ←[31mNoMethodError:←[0m ←[31mundefined method `authenticate' for nil:NilClass←[0m ←[36m # ./spec/models/user_spec.rb:103:in `block (4 levels) in &lt;top (require d)&gt;'←[0m ←[36m # ./spec/models/user_spec.rb:105:in `block (4 levels) in &lt;top (require d)&gt;'←[0m 5) User return value of authenticate method with invalid password ←[31mFailure/Error:←[0m ←[31mlet(:user_for_invalid_password) { found_user.a uthenticate("invalid") }←[0m ←[31mNoMethodError:←[0m ←[31mundefined method `authenticate' for nil:NilClass←[0m ←[36m # ./spec/models/user_spec.rb:103:in `block (4 levels) in &lt;top (require d)&gt;'←[0m ←[36m # ./spec/models/user_spec.rb:106:in `block (4 levels) in &lt;top (require d)&gt;'←[0m 6) User return value of authenticate method with valid password ←[31mFailure/Error:←[0m ←[31mit { should == found_user.authenticate(@user.e mail) }←[0m ←[31mNoMethodError:←[0m ←[31mundefined method `authenticate' for nil:NilClass←[0m ←[36m # ./spec/models/user_spec.rb:120:in `block (4 levels) in &lt;top (require d)&gt;'←[0m 7) User return value of authenticate method with invalid password ←[31mFailure/Error:←[0m ←[31mlet(:user_for_invalid_password) { found_user.a uthenticate("invalid") }←[0m ←[31mNoMethodError:←[0m ←[31mundefined method `authenticate' for nil:NilClass←[0m ←[36m # ./spec/models/user_spec.rb:124:in `block (4 levels) in &lt;top (require d)&gt;'←[0m ←[36m # ./spec/models/user_spec.rb:126:in `block (4 levels) in &lt;top (require d)&gt;'←[0m 8) User return value of authenticate method with invalid password ←[31mFailure/Error:←[0m ←[31mlet(:user_for_invalid_password) { found_user.a uthenticate("invalid") }←[0m ←[31mNoMethodError:←[0m ←[31mundefined method `authenticate' for nil:NilClass←[0m ←[36m # ./spec/models/user_spec.rb:124:in `block (4 levels) in &lt;top (require d)&gt;'←[0m ←[36m # ./spec/models/user_spec.rb:127:in `block (4 levels) in &lt;top (require d)&gt;'←[0m 9) User with a password that's too short ←[31mFailure/Error:←[0m ←[31mit { should be_valid }←[0m ←[31mexpected valid? to return true, got false←[0m ←[36m # ./spec/models/user_spec.rb:112:in `block (3 levels) in &lt;top (require d)&gt;'←[0m Finished in 8.5 seconds ←[31m23 examples, 9 failures←[0m Failed examples: ←[31mrspec ./spec/models/user_spec.rb:31←[0m ←[36m# User ←[0m ←[31mrspec ./spec/models/user_spec.rb:60←[0m ←[36m# User when email format is va lid should be valid←[0m ←[31mrspec ./spec/models/user_spec.rb:99←[0m ←[36m# User return value of authent icate method with valid password ←[0m ←[31mrspec ./spec/models/user_spec.rb:105←[0m ←[36m# User return value of authen ticate method with invalid password ←[0m ←[31mrspec ./spec/models/user_spec.rb:106←[0m ←[36m# User return value of authen ticate method with invalid password ←[0m ←[31mrspec ./spec/models/user_spec.rb:120←[0m ←[36m# User return value of authen ticate method with valid password ←[0m ←[31mrspec ./spec/models/user_spec.rb:126←[0m ←[36m# User return value of authen ticate method with invalid password ←[0m ←[31mrspec ./spec/models/user_spec.rb:127←[0m ←[36m# User return value of authen ticate method with invalid password ←[0m ←[31mrspec ./spec/models/user_spec.rb:112←[0m ←[36m# User with a password that's too short ←[0m </code></pre> <p>My User_spec.rb</p> <pre><code>require 'spec_helper' describe User do before do @user = User.new(name: "Example User", email: "user@example.com", password: "foobar", password_confirmation: "foobar") end subject { @user } it { should respond_to(:name) } it { should respond_to(:email) } it { should respond_to(:password_digest) } it { should respond_to(:password) } it { should respond_to(:password_confirmation) } it { should respond_to(:authenticate) } it { should be_valid } describe "When name is not present" do before { @user.name = " " } it { should_not be_valid } end describe "when email is not present" do before { @user.email = " " } it { should_not be_valid} end describe "when name is too long" do before { @user.name = "a" * 51 } it { should_not be_valid } end describe "when email format is invalid" do it "should be invalid" do addresses = %w[user@foo,com user_at_foo.org example.user@foo. foo@bar_baz.com foo@bar+baz.com] addresses.each do |invalid_address| @user.email = invalid_address @user.should_not be_valid end end end describe "when email format is valid" do it "should be valid" do addresses = %w[user@foo.COM A_US-ER@f.b.org frst.lst@foo.jp a+b@baz.cn] addresses.each do |valid_address| @user.email = valid_address @user.should be_valid end end end describe "when email addresses is already taken" do before do user_with_same_email = @user.dup user_with_same_email.email = @user.email.upcase user_with_same_email.save end it { should_not be_valid } end describe "when password is not present" do before { @user.password = @user.password_confirmation = " "} it { should_not be_valid } end describe "when password doesn't match confirmation" do before { @user.password_confirmation = "mismatch" } it { should_not be_valid } end describe "when password confirmation is nil" do before { @user.password_confirmation = nil } it { should_not be_valid } end describe "return value of authenticate method" do before { @user.save } let(:found_user) { User.find_by_email(@user.email) } describe "with valid password" do it { should == found_user.authenticate(@user.password) } end describe "with invalid password" do let(:user_for_invalid_password) { found_user.authenticate("invalid") } it { should_not == user_for_invalid_password } specify { user_for_invalid_password.should be_false } end end describe "with a password that's too short" do before { @user.password = @user.password_confirmation = "a" * 5 } it { should be_valid } end describe "return value of authenticate method" do before { @user.save } let(:found_user) { User.find_by_email(@user.email) } describe "with valid password" do it { should == found_user.authenticate(@user.email) } end describe "with invalid password" do let(:user_for_invalid_password) { found_user.authenticate("invalid") } it { should_not == user_for_invalid_password } specify { user_for_invalid_password.should be_false } end end end My user.rb model: class User &lt; ActiveRecord::Base attr_accessible :email, :name, :password, :password_confirmation has_secure_password before_save { |user| user.email = email.downcase } validates :name, presence: true, length: { maximum: 50 } VALID_EMAIL_REGEX = /\A[w+\-.]+@[a-z\d\-.]+\.[a-z]+\z/i validates :email, presence: true, format: { with: VALID_EMAIL_REGEX }, uniqueness: { case_sensitive: false } validates :password, presence: true, length: { minimum: 6 } validates :password_confirmation, presence: true end </code></pre> <p>Please anyone help! I've stucked on this problem for about two weeks and still have no idea what to do.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USszatan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COPost your user model
      singulars
      1. PORails 3 tutorial chapter 6 strange Rspec failures
      1. USMisha M
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload