Comments on: First Rails gotcha: Rails doesn’t tear down fixture data

By: highatmosray

highatmosray — Wed, 21 May 2008 14:56:17 +0000

Great… but it seems that this does not work completely. However when i put
’self.use_transactional_fixtures = false’ it does.
So somehow everything is in a transaction and therefor cannot be deleted, which makes sense because you cannot delete something that is not there yet.
The problem i ran into next was the data created in my tests was still in the DB.
My first guess was to perform a rollback and close the transaction like you normally would and then call the delete_all. This worked for me

def teardown
ActiveRecord::Base.connection.rollback_db_transaction
Fixtures.all_loaded_fixtures.each do |table_name, fixtures|
klass = Module.const_get(table_name.to_s.classify)
klass.delete_all
end
end

By: Jamie Flournoy

Jamie Flournoy — Wed, 07 Nov 2007 18:19:33 +0000

Thanks! I’m currently preloading all fixtures at the start of the test suite and letting Rails roll back the tests’ changes each time, but your code is helpful in case someone wants to do the per-test load-then-drop method.

Presumably if there are foreign keys then there would need to be some additional code that made the ordering correct.

By: Kristian Hellquist

Kristian Hellquist — Wed, 07 Nov 2007 09:23:52 +0000

'''Monkeypatching Rails so that all fixtures that have been loaded are deleted when the test class has finished running''' in your test_helper.rb:

class Test::Unit::TestCase
  def teardown
    Fixtures.all_loaded_fixtures.each do |table_name, fixtures|      
      klass = Module.const_get(table_name.to_s.classify) 
      klass.delete_all
    end
  end
end