[rspec-users] Should I be using database_cleaner to tear down data in RSpec 2.0 + Rails 3.0?
dchelimsky at gmail.com
Sat Jun 5 17:17:10 EDT 2010
On Jun 5, 2010, at 4:20 PM, Brian Cardarella wrote:
> Ok, something else is going on because I just generated a brand new
> app with rspec-2.0.beta.10 and the transactions are working just fine.
> Sorry about that, I'll track down the issue.
> - Brian
> On Jun 5, 4:12 pm, Brian Cardarella <bcardare... at gmail.com> wrote:
>> Sorry, forgot to answer the other question. I am using ActiveRecord.
>> Just a greenfield Rails 3.0.0.beta3 app
>> - Brian
>> On Jun 5, 3:42 pm, David Chelimsky <dchelim... at gmail.com> wrote:
>>> On Jun 5, 2010, at 3:34 PM, Brian Cardarella wrote:
>>>> On Jun 5, 2:12 pm, David Chelimsky <dchelim... at gmail.com> wrote:
>>>>> On Jun 5, 2010, at 12:42 PM, Brian Cardarella wrote:
>>>>>> Subject pretty much asks the question
>>>>> You _can_, but if you use ActiveRecord and start off with a clean DB, you can use_transactional_examples (alias for use_transactional_fixtures, which defaults to true in beta.10, but will default to false in beta.11).
>>>> I'm not seeing that behavior.
>>>> I have beta.10 and without using database_cleaner data is persisting
>>>> after each spec and from suite run to suite run. I thought
>>>> database_cleaner would resolve the issue but it doesn't seem to.
>>> I _am_ seeing that behaviour :)
>>> Are you using AR? What does your spec_helper look like?
>>> This cucumber feature passes:
>>> Not sure what's up, but there is something different about your environment.
>>> rspec-users mailing list
>>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users