Undefined methods: has_selector? and flunk

Testing RSpec
#1

I’m in the process of updating an app for Rails 3.0 and rspec-rails
2.0.0.beta20. When I’m running my specs (rake spec) I get a large number
of errors caused by two undefined methods

undefined method `has_selector?’ for #String:0x7fdbd0b5b270

undefined method `flunk’ for
#RSpec::Core::ExampleGroup::Nested_15::Nested_1::Nested_2::Nested_2:0x7fdbd0c48fe8

I’ve seen the upgrade notice for beta20 and now include capybara
explicitly in the test group of my Gemfile. The version of capybara on
my system is 0.3.9 and noticeably, it does not define has_selector? (or
have_selector? as webrat does).

Presumably, this is all just a dependency problem, but I have no clear
idea where to look.

Michael

–
Michael S.
mailto:[email protected]
http://www.schuerig.de/michael/

#2

On Sep 1, 2010, at 7:49 AM, Michael S. wrote:

I’m in the process of updating an app for Rails 3.0 and rspec-rails
2.0.0.beta20. When I’m running my specs (rake spec) I get a large number
of errors caused by two undefined methods

undefined method `has_selector?’ for #String:0x7fdbd0b5b270

See http://github.com/rspec/rspec-rails/issues/issue/190

undefined method `flunk’ for
#RSpec::Core::ExampleGroup::Nested_15::Nested_1::Nested_2::Nested_2:0x7fdbd0c48fe8

Please report this one to http://github.com/rspec/rspec-rails/issues
including the spec, code, versions, and full backtrace of the error.

Thx,
David

#3

On Wednesday 01 September 2010, David C. wrote:

On Sep 1, 2010, at 7:49 AM, Michael S. wrote:

I’m in the process of updating an app for Rails 3.0 and rspec-rails
2.0.0.beta20. When I’m running my specs (rake spec) I get a large
number of errors caused by two undefined methods

undefined method `has_selector?’ for #String:0x7fdbd0b5b270

See http://github.com/rspec/rspec-rails/issues/issue/190

Thanks, I’ve just switched to webrat. Things look much better now.

undefined method `flunk’ for

#<RSpec::Core::ExampleGroup::Nested_15::Nested_1::Nested_2::Nested_
2:0x7fdbd0c48fe8>

Please report this one to http://github.com/rspec/rspec-rails/issues
including the spec, code, versions, and full backtrace of the error.

http://github.com/rspec/rspec-rails/issues/issue/192

Michael

–
Michael S.
mailto:[email protected]
http://www.schuerig.de/michael/