Pelle Braendgaard wrote:
> I have made a fix to fixture scenarios which fixes that particular
> problem. I've made it available here:
>
> http://github.com/pelle/fixture-scenarios/tree/master
It works!
Thank you very, very much, Pelle.
Giuseppe
--
Posted via http://www.ruby-forum.com/.
It was this change included in rspec 1.1.12 that caused the problem:
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/620-fixture_path-moved-from-testunittestcase-to-activesupporttestcase
Basically rspec extends ActiveSupport::TestCase instead of Test::Unit:TestCase.
I have made a fix t
> Is the git tree any different than the svn one?
> http://github.com/mojombo/fixture-scenarios/tree/master
> Scott
Hi Scott, I checked, and the two trees are actually identical.
It seems that while fixture_scenarios has not changed since around April
2007, changes in rspec since v.1.1.4 have cr
Giuseppe Bertini wrote:
Hello there,
is anyone still using fixture_scenarios with RSpec these days? They
don't seem to coexist peacefully anymore.
I just created a new rails (2.2.2) app, generated an rspec_scaffold
(with v. 1.1.12), and verified that all specs pass.
But if I then install the f
Hello there,
is anyone still using fixture_scenarios with RSpec these days? They
don't seem to coexist peacefully anymore.
I just created a new rails (2.2.2) app, generated an rspec_scaffold
(with v. 1.1.12), and verified that all specs pass.
But if I then install the fixture_scenarios plugin:
