Fearless Fool wrote: [...] > Marnen, maybe I misunderstand you, but even if I knew a priori which > TimeDimension records my tests were going to use,
Uh...what? How can you *not* know a priori how your tests should behave? If you don't know the results you expect a priori, then you can't write proper tests. It sounds like there's something wrong, or at least strange, with your testing methodology. Can you post some example test code so I can see how you're using these records? > it's a PITA to > generate TimeDimension records piecemeal (what day did Easter fall on in > 2005?) Who cares? Just generate a TimeDimension record that has the properties you need for the particular test. If that means saying Easter fell in December, that's perfectly OK. > > Furthermore, I have other large constant tables such as the location of > FAA certified airports in North America, cobbled from multiple sources. > Again, it would be a pain to figure out exactly which ones my test code > will reference and then ETL their records on demand. You shouldn't need to ever do that in your tests. Just create fake data that has the properties you want to test. 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.
