> Since fixtures and database schema do not change that often it should > be possible to just load the fixtures once to the database and, if all > the tests run inside a transaction, on the next test run just load some > cache where only the fixture keys are held because technically that is > the only data that the database at that point does not already have. > > Any ideas on the feasability of something like this?
I like that idea. Since most people just run all tests inside a big transaction anyway, there should rarely be changes to the fixtures or the database. Keeping those stable when that's the case would be great. But we certainly should think about the transaction case. It's quite valuable to be able to test transactions. So perhaps we can have a special block or something that you could wrap around your test if it uses transactions and make sure that all pre- and post-cleanup is done. It'll make that one test run slowly, but that's fine. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
