Forum: RSpec Help with some basics

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Andrew T. (Guest)
on 2009-04-30 18:46
(Received via mailing list)
I'm suddenly getting an error on my specs

/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_methods.rb:24:in
`description': No description supplied for example declared on
/home/andrew/dev/rhythm/website/spec/models/product_template_spec.rb:4
(Spec::Example::NoDescriptionError)
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_methods.rb:51:in
`execute'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_group_methods.rb:207:in
`run_examples'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_group_methods.rb:205:in
`each'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_group_methods.rb:205:in
`run_examples'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_group_methods.rb:103:in
`run'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/runner/example_group_runner.rb:23:in
`run'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/runner/example_group_runner.rb:22:in
`each'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/runner/example_group_runner.rb:22:in
`run'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/runner/options.rb:119:in
`run_examples'
  from
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/runner/command_line.rb:9:in
`run'
  from /usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/bin/spec:4
  from /usr/local/bin/spec:19:in `load'
  from /usr/local/bin/spec:19


The spec is as follows (using Remarkable)
require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')

describe ProductTemplate do
  it { should belong_to(:account) }

  it { should validate_presence_of(:account) }
  it { should validate_presence_of(:name) }
  it { should validate_presence_of(:cost) }

  it { should validate_length_of(:name).within(1..100) }

  it { should validate_uniqueness_of(:name) }
end

I've just updated to the latest versions of rspec, rspec-rails and
remarkable


Not sure what I'm doing wrong here.

Thanks

Andrew
David C. (Guest)
on 2009-04-30 19:00
(Received via mailing list)
On Thu, Apr 30, 2009 at 9:44 AM, Andrew T.
<removed_email_address@domain.invalid> wrote:
>        from 
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_group_methods.rb:205:in
> `run'
> require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
>  it { should validate_uniqueness_of(:name) }
> end
>
> I've just updated to the latest versions of rspec, rspec-rails and remarkable
>
>
> Not sure what I'm doing wrong here.

That happens when a matcher doesn't supply a description (which is
required), but it looks like the remarkable matchers do, so I'm not
sure what's up with that.

How are you running it? What command?
Andrew T. (Guest)
on 2009-04-30 23:56
(Received via mailing list)
It gives me the same error when I run
rake spec
spec specs/
or
autospec

It also gives the same error with specs like
it { should_not be_nil }
and
it { should respond_to(:name) }


On Thursday, April 30, 2009, David C. <removed_email_address@domain.invalid>
wrote:
>>        from 
/usr/local/lib/ruby/gems/1.8/gems/rspec-1.2.5/lib/spec/example/example_group_methods.rb:207:in
>> `each'
>>
>>  it { should validate_length_of(:name).within(1..100) }
> required), but it looks like the remarkable matchers do, so I'm not
>> removed_email_address@domain.invalid
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> removed_email_address@domain.invalid
> http://rubyforge.org/mailman/listinfo/rspec-users
>

--
Andrew T.
http://ramblingsonrails.com
http://www.linkedin.com/in/andrewtimberlake

"I have never let my schooling interfere with my education" - Mark Twain
David C. (Guest)
on 2009-05-01 00:05
(Received via mailing list)
On Thu, Apr 30, 2009 at 2:55 PM, Andrew T.
<removed_email_address@domain.invalid> wrote:
> It gives me the same error when I run
> rake spec
> spec specs/
> or
> autospec
>
> It also gives the same error with specs like
> it { should_not be_nil }
> and
> it { should respond_to(:name) }

Those are internal to rspec and I can assure you they have descriptions.

I'm mystified. Anybody else on this list have a similar experience?
Andrew T. (Guest)
on 2009-05-01 07:23
(Received via mailing list)
On Thu, Apr 30, 2009 at 10:04 PM, David C. 
<removed_email_address@domain.invalid>
wrote:
>> and
>> it { should respond_to(:name) }
>
> Those are internal to rspec and I can assure you they have descriptions.
>
> I'm mystified. Anybody else on this list have a similar experience?
>
>

Managed to find the problem, the class ProductTemplate wasn't being
loaded so "it" wasn't working on an object.
The error is not very useful in this situation but I'm moving forward
again.

Thanks for the help

Andrew T.
http://ramblingsonrails.com
http://www.linkedin.com/in/andrewtimberlake

"I have never let my schooling interfere with my education" - Mark Twain
Samuel S. (Guest)
on 2009-05-01 20:57
>
> Managed to find the problem, the class ProductTemplate wasn't being
> loaded so "it" wasn't working on an object.
> The error is not very useful in this situation but I'm moving forward
> again.
>

How did you solved it? I'm having the same problem.
Andrew T. (Guest)
on 2009-05-02 07:56
(Received via mailing list)
On Fri, May 1, 2009 at 6:57 PM, Samuel Soares flores
<removed_email_address@domain.invalid> wrote:
>
>>
>> Managed to find the problem, the class ProductTemplate wasn't being
>> loaded so "it" wasn't working on an object.
>> The error is not very useful in this situation but I'm moving forward
>> again.
>>
>
> How did you solved it? I'm having the same problem.
> --

What I've found is that occasionally when there is a problem loading
the base class, the errors become very cryptic.
You can get to the base error by adding a very simple spec in the form
of:
it "" { ... }

In my specific case, my model was in a different schema and so
ActiveRecord couldn't find the table in the database.

Andrew T.
http://ramblingsonrails.com
http://www.linkedin.com/in/andrewtimberlake

"I have never let my schooling interfere with my education" - Mark Twain
This topic is locked and can not be replied to.