On Friday, October 5, 2012 9:56:34 AM UTC+2, Daniele Procida wrote: > > On Thu, Oct 4, 2012, Evan Brumley <[email protected] <javascript:>> > wrote: > > >django-dynamic-fixture can also help a lot in this situation: > >http://paulocheque.github.com/django-dynamic-fixture/ > > > >Certainly beats having to futz around with fixtures. > > Thanks - there seem to be a lot of tools to generate test data in various > ways, such as <https://github.com/dnerdy/factory_boy>. > > However I am still puzzled by the question at a slightly higher level, > about strategy - is it better to create a large collection of data once, > and to test the behviour of the system against the various combinations of > data in it, or to create a lengthy succession of smaller collections of > data,containing only the material needed for the particular combination > being tested each time? >
The problem you raising, is I think the problematic of unit-tests which tests a specific feature of an application versus integration aka. several-applications-wide tests which tests that a user workflow works properly like I put create a model, celery process it, then I (or another user) change the model, then I send an email, I get an hardbounce etc...). Anyway, like I said in the other mail, I do think that manual is better. HTH, Amirouche -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/mrNzXmWemz8J. 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/django-users?hl=en.
