public
Description: RSpec's Story Runner (formerly RBehave, presently replaced by Cucumber)
Home | Edit | New

Home

Welcome to the rspec-stories wiki!

Troubleshooting

NoMethodError in scenario_failed

With RSpec 1.2.6 I get the following exception if a scenario fails:


/home/sam/projects/ovc/vendor/gems/rspec-stories-1.0.0/lib/spec/runner/formatter/story/plain_text_formatter.rb:80:in `scenario_failed': You have a nil object when you didn't expect it! (NoMethodError)
The error occurred while evaluating nil.tweak_backtrace  from /home/sam/projects/ovc/vendor/gems/rspec-stories-1.0.0/lib/spec/story/runner/scenario_runner.rb:27:in `run'

It looks like a backtrace_tweaker object got removed from RSpec internals.

I have a fork of rspec-stories which fixes this error, while preserving the existing behaviour with older versions of RSpec.

“no such file to load — spec/rails/story_adapter”

When running stories for a Rails app (:type => RailsStory), you might get the following error before any steps run:


/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- spec/rails/story_adapter (MissingSourceFile)
	from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `polyglot_original_require'
	from /usr/lib/ruby/gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in `require'
[...]

story_adapter.rb used to live in rspec-rails, but it was removed around version 1.2.5, and didn’t find a new home.

I have a fork of rspec-stories which includes this file, taken from rspec-rails just before it was removed and unceremoniously dumped into rspec-stories.

Last edited by samstokes, Mon May 11 05:30:43 -0700 2009
Home | Edit | New
Versions: