From: Phlip Date: 2009-01-12T02:44:25+09:00 Subject: Re: reccommended work flow for unit tests and databases in ruby David A. Black wrote: > I'd have to see the code to know exactly what's going on. Is it a > problem reconciling foreign key references? It's a general, structural question, so I will ask it a different way. This thread seems to propose one can borrow ActiveRecord, plus fixtures and migrations, and use them in a Ruby project that is (shocked gasp) not Rails. If so, then doing this, in Rails, should be easy, too! class MyUnitTestSuite < ActiveSupport::TestCase fixtures :foos def setup fixtures :bars end ... end For whatever reason, we want to load some fixtures the old-fashioned way, and some fixtures optionally. Maybe in the top of a test case, or maybe conditionally in a setup. Or whatever. If we promise the OP they can borrow ActiveRecord facilities, then borrowing them should indeed be easy. But whenever I try to call or re-use or re-wrap the methods inside fixtures, they screw up in horrible ways. This _might_ be a sign of coupling! -- Phlip