Marnen Laibow-Koser wrote: > [snip] > Sent from my iPhone Wow - that's some agile thumbs you've got there.
Yes, I could create mock classes that fake the data for exactly the items I need. But: Since I already have the static tables (and have tested them), wouldn't that be analogous to writing a Math::sin(x) function that is defined only for specific values of x? To extend the analogy, Math::sin(x) is not part of the business logic of my app, and I should not be testing it any more than I should be testing whether or not :belongs_to generates the correct methods in ActiveRecord. In these circumstances, I'd maintain that I'm MORE likely to introduce errors in my tests by writing mock classes when stable, proven data already exists. Can't you just be happy that I'm not using fixtures now? :) - ff -- 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.
