Yeah, we had that problem yeserday... We had to rake db:prepare before any
test.... I would change it to what it wants.


On Wed, Oct 2, 2013 at 10:29 AM, lauyeung <notifications@github.com> wrote:

> In spec/features/user_signs_up_spec.rb:
>
> > +      fill_in("Password confirmation", with: '12345678', :match => :prefer_exact)
> > +      click_button "Sign up"
> > +
> > +      expect(page).to have_content("You're in!")
> > +      expect(page).to have_content("Sign Out")
> > +      expect(User.count).to eql(prev_count +1)
> > +
> > +    end
> > +
> > +    scenario "with invalid info" do
> > +      prev_count = User.count
> > +      visit root_path
> > +      click_link "Sign Up"
> > +      click_button "Sign up"
> > +
> > +      expect(page).should have_content("can't be blank")
>
> I'm getting a deprecation warning? Should this be changed?
>
> DEPRECATION: `expect { }.should` is deprecated. Use `expect { }.to` instead. Called from /Users/lauyeung/Dropbox/launchacademy/work/gem_reviewer/spec/features/user_signs_up_spec.rb:40:in `block (2 levels) in <top (required)>'.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/lauyeung/gem_reviewer/pull/2/files#r6716297>
> .
>