[rspec-users] rspec2 not working with shoulda

[Nadal]

I am using rails edge. I am using gem "rspec-rails", "= 2.0.0.beta.
19" .

I have following code at spec/models/user_spec.rb

require 'spec_helper'

describe User do

it { should validate_presence_of(:email) }

it { should validate_presence_of(:name) }

end

Here is my gemfile

group :development, :test do
gem 'factory_girl_rails', :git => 'git://github.com/thoughtbot/
factory_girl_rails'
gem 'shoulda'
gem "rspec-rails", "= 2.0.0.beta.19"
gem "cucumber-rails", "= 0.3.2"
gem "capybara"
gem "launchy"
end

I am getting following error message.

Failure/Error: it { should validate_presence_of(:email) }
undefined method `validate_presence_of' for
#<RSpec::Core::ExampleGroup::Nested_2:0x10a63e3a8 @__memoized={}>
# ./spec/models/user_spec.rb:5
_______________________________________________
rspec-users mailing list
rspec...@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users

[David Chelimsky]

On Aug 11, 2010, at 2:31 AM, Nadal wrote:

> I am using rails edge. I am using gem "rspec-rails", "= 2.0.0.beta.
> 19" .
>
> I have following code at spec/models/user_spec.rb
>
> require 'spec_helper'
>
> describe User do
>
> it { should validate_presence_of(:email) }
>
> it { should validate_presence_of(:name) }
>
> end
>
>
> Here is my gemfile
>
> group :development, :test do
> gem 'factory_girl_rails', :git => 'git://github.com/thoughtbot/
> factory_girl_rails'
> gem 'shoulda'
> gem "rspec-rails", "= 2.0.0.beta.19"
> gem "cucumber-rails", "= 0.3.2"
> gem "capybara"
> gem "launchy"
> end
>
> I am getting following error message.
>
>
> Failure/Error: it { should validate_presence_of(:email) }
> undefined method `validate_presence_of' for
> #<RSpec::Core::ExampleGroup::Nested_2:0x10a63e3a8 @__memoized={}>
> # ./spec/models/user_spec.rb:5

Sounds like shoulda is not registering itself properly with rspec-2. I'd check with the should list: http://groups.google.com/group/shoulda.

HTH,
David

[David Chelimsky]

Also - the subject line is backwards - it shoulda been "shoulda not working with rspec-2" ;)

[Craig Demyanovich]

On Wed, Aug 11, 2010 at 10:38 AM, David Chelimsky <dchel...@gmail.com> wrote:

Also - the subject line is backwards - it shoulda been "shoulda not working with rspec-2" ;)

It's been a long time since I tried shoulda, but I used to like to give the advice, "you shoulda used RSpec instead." ;-)

Hope you get everything working, Nadal.

Regards,

Craig 

[Nadal]

I posted a question on shoulda forum. It is under moderation so I
don't have a link yet.

To the people who do not use shoulda: How would you write a test for
above case. I assume it would require set up a subject, set nil value,
and then see if there is an error message. I still think that for such
cases should macro is succint and does it job well unless I am missing
some new feature of rspec2.

Thanks

On Aug 11, 12:28 pm, Craig Demyanovich <cdemyanov...@gmail.com> wrote:

> On Wed, Aug 11, 2010 at 10:38 AM, David Chelimsky <dchelim...@gmail.com>wrote:
>
>
>
> > Also - the subject line is backwards - it shoulda been "shoulda not working
> > with rspec-2" ;)
>
> It's been a long time since I tried shoulda, but I used to like to give the
> advice, "you shoulda used RSpec instead." ;-)
>
> Hope you get everything working, Nadal.
>
> Regards,
> Craig
>

> _______________________________________________
> rspec-users mailing list
> rspec-us...@rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

[Craig Demyanovich]

On Wed, Aug 11, 2010 at 12:53 PM, Nadal <node...@gmail.com> wrote:

I posted a question on shoulda forum. It is under moderation so I
don't have a link yet.

To the people who do not use shoulda: How would you write a test for
above case. I assume it would require set up a subject, set nil value,
and then see if there is an error message. I still think that for such
cases should macro is succint and does it job well unless I am missing
some new feature of rspec2.

I don't yet use RSpec 2, but I don't think you're missing anything. Shoulda may very well be a good fit for these kinds of examples.

Since you asked, here's how I currently write examples like the ones you posted.

require 'spec_helper'

describe User, "being valid" do

  it "requires an email" do

    user = User.new(:email => nil)

    user.should_not be_valid

    user.should have(1).error_on(:email)

  end

  

  it "requires a name" do

    user = User.new(:name => nil)

    user.should_not be_valid

    user.should have(1).error_on(:name)

  end

end

Regards,

Craig 

[Phillip Koebbe]

That's exactly what I used to do, also, until I switched to Remarkable.
Now it's:

before :each do
@user = User.create(valid_user_hash)
end

should_validate_presence_of :first_name
should_validate_presence_of :last_name
should_validate_presence_of :email
should_validate_uniqueness_of :email, :case_sensitive => false
should_validate_format_of_email

One thing I have come to appreciate about this is being able to copy the
should_* statements to my model and, using TextMate's column editing
mode, remove the 'should_' and add an 's' at the end of 'validate' and
I'm done. For all of the validations that Remarkable supports, the same
options are supported as well. That's actually why I switch from Shoulda
to Remarkable a year or so ago (things might have changed in Shoulda by
now, though): Not all validation options were supported in Shoulda.

Peace,
Phillip