On Tue, Jul 13, 2010 at 10:45, Colin Law <[email protected]> wrote: > On 13 July 2010 14:45, Dave Aronson <[email protected]> wrote: >>... >> *If* a given database (or table or set of tables) is absolutely >> constant, so that it will not be added to or subtracted from during >> the course of any test, only referenced, as seems to be the case in >> FF's situation, then it is (IMVHO) sufficient to only clear-and-load >> it at the start of the entire suite, rather than incur the penalties >> of doing so on every test. Perhaps that could even be enforced (at >> least for the duration of the tests) with some triggers. > > So what happens if there is a bug that accidentally writes to that > table during a test?
Reread last sentence. :-) -Dave -- Specialization is for insects. | Professional: http://davearonson.com -Robert Anson Heinlein | Programming: http://codosaur.us -------------------------------+ Leadership: http://dare2xl.com Have Pun, Will Babble! -me | Et Cetera: http://davearonson.net -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
