Remember these things should use transactions, and may do that by
default - the database will be wiped clean once the features have run.
On 9 Sep 2008, at 18:22, Tim Glen wrote:
Hey guys,
I'd never used RSpec Stories before, so I decided to follow the
apparent direction of the wind and
On Tue, Sep 9, 2008 at 7:45 PM, Matt Wynne [EMAIL PROTECTED] wrote:
Remember these things should use transactions, and may do that by default -
the database will be wiped clean once the features have run.
FWIW, When Cucumber is used with Rails it runs all scenarios in a transaction.
I haven't
On Tue, Sep 9, 2008 at 7:45 PM, Matt Wynne [EMAIL PROTECTED] wrote:
Remember these things should use transactions, and may do that by
default -
the database will be wiped clean once the features have run.
sorry - I wasn't trying to say that the database is empty after the
scenarios are
Before do
self.extend(FixtureReplacement)
end
I had previously tried this right in the steps file:
Before do
self.include(FixtureReplacement)
end
Actually - this turned out to almost the right thing. I just added
this to my env.rb:
`include FixtureReplacement`
Wrapping it in the Before
Did you see that my code uses extend?
Yes - tried both in my flailing about :)
If that still doesn't work, file a bug report.
http://rspec.lighthouseapp.com/projects/16211-cucumber/overview
It might be a FixtureReplacement bug, but I'll still look into it.
Could it be that
Did you see that my code uses extend?
Yes - tried both in my flailing about :)
If that still doesn't work, file a bug report.
http://rspec.lighthouseapp.com/projects/16211-cucumber/overview
It might be a FixtureReplacement bug, but I'll still look into it.
Could it be that
