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. No need to pass any blocks about as arguments (I really hate that, but that could just be me). The syntax could not be simpler and less obtrusive. 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. On May 25, 9:00 pm, Marnen Laibow-Koser <[email protected]> wrote: > Ginty wrote: > > Hi All, > > > Shameless plug here, but just released my first gem which is a simple > > factory plugin a la Factory Girl, but which IMHO gives you much more > > control of your factory logic, check it out if interested: > > > Github:http://github.com/ginty/Cranky > > > Blog:http://www.hyperdecade.com/2010/05/26/cranky-at-factory-girl > > Interesting. What distinguishes this from Machinist/Fixjour/Fixture > Replacement? > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > -- > Posted viahttp://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.
