Mike B wrote in post #967999: > Thanks for the ideas. I might have to go that route if I can't get > this figured out. Either that or skip fixtures and have my test cases > completely load the database from scratch. > > Ideally I would like to stick with 'vanilla' rails as much as > possible. I've found that the more libraries you layer on top of your > app the harder it is for people to come along after you and maintain/ > enhance it.
That's not actually true in general, especially if you have decent test coverage. Personally, I'd rather maintain something with lots of (documented) libraries included than something with lots of reinvented wheels. Anyway, Colin is absolutely right. There is no reason to use fixtures and every reason to get rid of them. The Rails core team made a mistake in designing fixtures, and so they should be completely avoided. > > Mike Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] Sent from my iPhone -- Posted via http://www.ruby-forum.com/. -- 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.
