> Right now, the fixture-scenarios plugin is a step in the right > direction, but I wouldn't mid joining in in an effort to replace the > current Fixture system in rails completely, hell, I wouldn't mind it > breaking backwards-incompatibility if thats what it took.
Increasing the overhead required for editing fixtures never seemed like a good idea to me. I've always used fixtures as a way to store a 'representative' snapshots of my production system, and made my tests work accordingly. In this kind of usage the per-testcase fixtures overhead isn't needed as you can simply load the test database right at the beginning, and rollback the transaction after each testcase. The fixtures code is currently ripe for some tidying, but I'm not necessarily sold that they're more harm than good. The ability to get a named reference to a particular chunk of a known object graph, is completely killer. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
