Problem with Cucumber, Rails 3.0.5

rubyonrails-talk
1

Hi Everyone!

I just updated to rails 3.0.5 from rails 3.0.3, and I deleted my Gemfile.lock and runned “bundle install”

it appears that cucumber got a update, because I had to run “rails g cucumber:install” again to fix an error…

I’m using Factory Girl and Capybara too and I procured to include it in the cucumber’s env.rb file,

**now when I run the cucumber command, as I’m using capybara a browser windows is open, **

and then I noticed that the records weren’t created at all

with this, that didn’t happen before… my gem versions are:

Using rake (0.8.7)

Using aasm (2.2.0)

Using abstract (1.0.0)

Using activesupport (3.0.5)

Using builder (2.1.2)

Using i18n (0.5.0)

Using activemodel (3.0.5)

Using erubis (2.6.6)

Using rack (1.2.2)

Using rack-mount (0.6.14)

Using rack-test (0.5.7)

Using tzinfo (0.3.25)

Using actionpack (3.0.5)

Using mime-types (1.16)

Using polyglot (0.3.1)

Using treetop (1.4.9)

Using mail (2.2.15)

Using actionmailer (3.0.5)

Using arel (2.0.9)

Using activerecord (3.0.5)

Using activeresource (3.0.5)

Using archive-tar-minitar (0.5.2)

Using bundler (1.0.2)

Using celerity (0.8.8)

Using culerity (0.2.15)

Using nokogiri (1.4.4)

Using ffi (1.0.7)

Using childprocess (0.1.8)

Using json_pure (1.5.1)

Using rubyzip (0.9.4)

Using selenium-webdriver (0.1.4)

Using xpath (0.1.3)

Using capybara (0.4.1) from https://github.com/jnicklas/capybara.git (at 0.4.1)

Using columnize (0.3.2)

Using haml (3.0.25)

Using compass (0.10.6)

Using configuration (1.2.0)

Using diff-lcs (1.1.2)

Using json (1.5.1)

Using gherkin (2.3.5)

Using term-ansicolor (1.0.5)

Using cucumber (0.10.2)

Using cucumber-rails (0.4.0)

Using database_cleaner (0.6.6)

Using factory_girl (1.3.3)

Using thor (0.14.6)

Using railties (3.0.5)

Using factory_girl_rails (1.0.1)

Using formtastic (1.1.0)

Using haml-rails (0.3.4)

Using hirb (0.4.0)

Using hpricot (0.8.4)

Using rails (3.0.5)

Using jquery-rails (0.2.7)

Using launchy (0.4.0)

Using ruby_core_source (0.1.4)

Using linecache19 (0.5.11)

Using pg (0.10.1)

Using rspec-core (2.5.1)

Using rspec-expectations (2.5.0)

Using rspec-mocks (2.5.0)

Using rspec (2.5.0)

Using rspec-rails (2.5.0)

Using ruby-debug-base19 (0.11.24)

Using ruby-debug19 (0.11.6)

Using sexp_processor (3.0.5)

Using ruby_parser (2.0.6)

Using will_paginate (2.3.15)

I don’t know what could be the problem or where to look for in my code

any help?

greetings

2

I paste my stack overflow question… please help, i’m really stuck with this.

Hi Everyone,

I’m working on a rails project using, cucumber, capybara and factory girl, and recently updated from rails 3.0.3 to rails 3.0.5, deleted my Gemfile.lock, run the bundle install command, and it appears that cucumber or cucumber-rails got updated, because I had to run rails g cucumber:install --capybara --rspec again for and error that appeared.

The thing is that know when I run cucumber all my features fails because doesn’t find any records, not even the records I created (steps passes) in the Background section of the feature file.

I tried the same gem version combination creating a new project and everything worked, but in my current project don’t. What could be happening?

My gem versions are:

Using capybara (0.4.1) from https://github.com/jnicklas/capybara.git (at 0.4.1) Using cucumber (0.10.2) Using cucumber-rails (0.4.0) Using database_cleaner (0.6.6) Using factory_girl (1.3.3) Using factory_girl_rails (1.0.1) Using rails (3.0.5) Using rspec-core (2.5.1) Using rspec-expectations (2.5.0) Using rspec-mocks (2.5.0) Using rspec (2.5.0) Using rspec-rails (2.5.0)

3

Felipe Espinoza Castillo wrote in post #989076:

I paste my stack overflow question.... please help, i'm really stuck with this.

Hi Everyone,

in Gemfile set the version of cucumber-rails to 0.3.2

gem cucumber-rails, '=0.3.2'

run bundle update and roll back to cucumber 0.10.0. There are a bunch of things rolled up into 0.10.2 that were separate in 0.10.0 and I have had problems with it myself. If cucumber-0.10.0 was working for you then go back to that and let the new version of cucumber get itself sorted out before upgrading to it.