[rspec-users] be_true and be_false are suddenly undefined
Matt Wynne
matt at mattwynne.net
Thu Dec 24 04:14:21 EST 2009
On 24 Dec 2009, at 06:09, Doug wrote:
> after upgrading cucumber to 5.1 be_true and be_false are undefined
> switching to == true or == false works.
>
> ??? thanks.
The rails integration changed quite a bit for that release. See [1]
plus a few recent threads on this list.
It sounds like your specific problem is you don't have rspec's
matchers required anymore.
[1] http://wiki.github.com/aslakhellesoy/cucumber/upgrading
>
>
> Then there is an invalid item with 1 "upc"
> error # features/step_definitions/
> extract_steps.rb:
> 56
> undefined method `be_true' for
> #<ActionController::Integration::Session:0x104bc7820> (NoMethodError)
> ./features/step_definitions/extract_steps.rb:45:in `/^retrieve
> file$/'
>
>
>
> Then /^retrieve file$/ do
> basename = File.basename(@filename)
> ExtractReport.exists?(:file_name => basename).should ==
> true **** this is line 45
> @file = ExtractReport.find_by_file_name(basename)
> count = @file.record_count.to_i - 2 # count includes header and
> trailer
> @file.should have(count).items
> end
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
cheers,
Matt
http://mattwynne.net
+447974 430184
More information about the rspec-users
mailing list