Ginty wrote: > There are many factories, but this one is mine.....admittedly that > could be it to some extent! > > To me the benefits are: > > It is extremely light, which means it ain't gonna break on you when > other components of your test environment change. >
That sounds good. > No need to pass any blocks about as arguments (I really hate that, but > that could just be me). Er...what's wrong with blocks? I don't get the problem, and anyway, they're part of idiomatic Ruby... > > The syntax could not be simpler and less obtrusive. Great! > > It doesn't provide any magic for dealing with associations, you're own > your own. This was probably the #1 reason I developed this for myself, > I just never really felt in control of this from the other solutions I > tried (admittedly I haven't tried all of the ones on your list) and I > feel much happier writing tests when I know now exactly when and how > secondary instances are being generated. What's the point of factories that don't handle associations? That seems like a huge disadvantage. Part of the reason that I use factories is so I can just say Widget.make and get a fully viable Widget object, complete with required fields and associations. Otherwise, why bother? Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
