Do fixture_scenarios and RSpec peacibly coexist?

Railsters:

I just installed fixture_scenarios …

http://fixture-scenarios.googlecode.com/svn/trunk/fixture_scenarios

…into a project with some RSpec specifications. They all went
kablooey.

I didn’t even create a scenario; the system just started calling its
version
of fixtures(). The normal tests pass and the RSpec ones unanimously
emit:

TypeError in ‘Context (verbose situation…)’
can’t convert nil into String
…lib/fixture_scenarios.rb:108:in open' ..lib/fixture_scenarios.rb:108:inread_fixture_files’
…lib/fixture_scenarios.rb:66:in initialize' ..lib/fixture_scenarios.rb:29:increate_fixtures’
…lib/fixture_scenarios.rb:28:in create_fixtures' ..lib/fixture_scenarios.rb:26:increate_fixtures’
…lib/fixture_scenarios.rb:257:in load_fixtures' plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/model.rb:12:inbefore_eval’

The project is heavily scenario-dependent, so if it comes to a choice we
know which one we will save and which we will lose…

Has anyone encountered this? Can’t fixture_scenarios and RSpec live
together
in peace and harmony?


Phlip

On 9/20/07, Phlip [email protected] wrote:

of fixtures(). The normal tests pass and the RSpec ones unanimously emit:
plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/model.rb:12:in
`before_eval’

The project is heavily scenario-dependent, so if it comes to a choice we
know which one we will save and which we will lose…

Has anyone encountered this? Can’t fixture_scenarios and RSpec live together
in peace and harmony?

Sure they can. Just grab the current trunk or the next release (1.1.0

  • coming soon)