This list is for rails core discussion, so this question is probably better suited for rubyonrails-talk.
But I'll answer anyway (it would be great to get something like fixture_builder into Rails someday, none of the alternatives are good IMO): I use factories + fixtures via https://github.com/rdy/fixture_builder As for "mutually exclusive" datasets, depending on your app, maybe they can co-exist in the same fixture set. E.g., have them be separate "accounts" or "projects". If not, you can pass flags into fixture_builder to tell it which "set" of fixtures to build. -- Chad On Wed, Aug 6, 2014 at 5:16 AM, Pruss Wan <[email protected]> wrote: > Hi, > > Is there anybody out there who is really using fixtures exclusively? And > if so, how do you deal with scenarios when there is a need for multiple > fixture sets? (datasets that are mutually exclusive) Or is that the part > where the more popular factories come in? > > For those who are wondering why I even bother, I am in a situation where I > have plenty of real data to test and debug with, and if these could be > extracted to fixtures which are maintainable, there might be some value in > this approach for integration tests. > > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
