Command failed with status (1) event (which, in the instance of failing or pending steps, Cucumber triggers by design for the benefit of CI tools).
Am I missing something incredibly obvious? Is there a way for a BDD newcomer to look deeper into the issues (the stack trace just shows the standard rake error when Cucumber fails).
- rvm 1.9.2-head
- gem 'rails', '3.0.0.rc'
- gem 'cucumber'
- gem 'cucumber-rails'
- gem 'capybara'
- gem 'culerity'
- gem 'celerity', :require => nil