Package: django-autofixture-squad
This app aims to provide a simple way of loading masses of randomly generated
test data into your development database. You can use a management command to
load test data through command line.It is namedautofixturebecause it is based on  django’s fixtures. Withoutautofixtureyou add test data through the admin to see how the non-static
pages on your site look. You export data by usingdumpdatato
send it to your colleagues or to preserve it before you make amanage.py reset appand so on. As your site grows in complexity the process of adding
and re-adding data becomes more and more annoying.This is where autofixtures will help!RequirementsWe require and support Django 1.4 to 1.9InstallationYou must make theautofixturepackage available on your python path.
Either drop it into your project directory or install it from the python
package index withpip installdjango-autofixture. You can also useeasy_installdjango-autofixtureif you don’t have pip available.To use the management command you must add'autofixture'to theINSTALLED_APPSsetting in your django settings file. You don’t need to do
this if you want to use theautofixturepackage only as library.Management commandTheloadtestdataaccepts the following syntax:python manage.py loadtestdata [options] app.Model:# [app.Model:# ...]It’s nearly self explanatory. Supply names of models, prefixed with its app
name. After that, place a colon and tell the command how many objects you want
to create. Here is an example of how to create three categories and twenty
entries for your blogging app:python manage.py loadtestdata blog.Category:3 blog.Entry:20Voila! You have ready-to-use testing data populated to your database. The
model fields are filled with data by producing randomly generated values
depending on the type of the field. E.g. text fields are filled with lorem
ipsum dummies, date fields are populated with random dates from the last
year etc.There are a few command line options available. Mainly to control the
behavior of related fields. If foreingkey or many to many fields should be
populated with existing data or if the related models are also generated on
the fly. Please have a look at the help page of the command for more
information:python manage.py help loadtestdataUsing autofixtures as a tool for unittestsTesting the behavior of complex models has always bugged me. Sometimes models
have many restrictions or many related objects which they depend on. One
solution would be to use traditional fixtures dumped from your production
database. But while in development when database schemes are changing
frequently, it can be time consuming and sometimes difficult to deep track of
changes and what each dump contains.Autofixtures to the rescue!Let’s start with the basics. We create anAutoFixtureinstance for theEntrymodel and tell it to create ten model instances:>>> from autofixture import AutoFixture
>>> fixture = AutoFixture(Entry)
>>> entries = fixture.create(10)Here are further examples for newer developers.I have aListingmodel and I want it populated with 10 objects.>>> from autofixture import AutoFixture
>>> fixture = AutoFixture(Listing)
>>> entries = fixture.create(10)Here I’ve added field values which allow you to default a field to a certain
value rather than the random entries supplied byautofixture.Generic Example including field_values:from <yourapp>.models import <your model>
fixture = AutoFixture(<your model>, field_values={'<your field name>':<value>})Specific example:from main.models import Listing
fixture = AutoFixture(Listing, field_values={'needed_players': randint(2,10)})
entries=fixture.create(30)In the above, I wanted the'needed_players'(in the Session model) to have
only numbers between 2 and 10, but I could have put{'needed_players': 5}if I had wanted all'needed_players'instances to be5.Now you can play around and test your blog entries. By default, dependencies
of foreignkeys and many to many relations are populated by randomly selecting
an already existing object of the related model. But, what if you don’t have
one yet?  You can provide thegenerate_fkattribute which allows the
autofixture instance to follow foreignkeys by generating new related models:fixture = AutoFixture(Entry, generate_fk=True)This generates new instances forallforeignkey fields ofEntry. Unless
the model has a foreign key reference to itself, wherein the field will be set
to None if allowed or raise aCreateInstanceError. This is to prevent max
recursion depth errors. It’s possible to limit this behaviour to single
fields:fixture = AutoFixture(Entry, generate_fk=['author'])This will only create new authors automatically and doesn’t touch other
tables. The same is possible with many to many fields. But you need to
additionally specify how many objects should be created for the m2m relation:fixture = AutoFixture(Entry, generate_m2m={'categories': (1,3)})All created entry models get one to three new categories assigned.Setting custom values for fieldsAs shown the the examples above, it’s often necessary to have a specific field
contain a specific value. This is easily achieved with thefield_valuesattribute ofAutoFixture:fixture = AutoFixture(Entry,
    field_values={'pub_date': datetime(2010, 2, 1)})Limiting the set of models assigned to a ForeignKey fieldYou could, for example, limit the Users assigned to a foreignkey field to only
non-staff Users. Or create Entries for all Blogs not belonging to Yoko Ono.
Use the same construction asForeignKey.limit_choices_toattribute:from autofixture import AutoFixture, generators
fixture = AutoFixture(Entry, field_values={
    'blog': generators.InstanceSelector(
        Blog,
        limit_choices_to={'name__ne':"Yoko Ono's blog"})
})Custom autofixturesTo have custom autofixtures for your model, you can easily subclassAutoFixturesomewhere (e.g. in myapp/autofixtures.py)from models import MyModel
from autofixture import generators, register, AutoFixture

class MyModelAutoFixture(AutoFixture):
    field_values = {
        'name': generators.StaticGenerator('this_is_my_static_name'),
    }

register(MyModel, MyModelAutoFixture)Then,loadtestdatawill automatically use your custom fixtures.python manage.py loadtestdata app.MyModel:10You can load allautofixtures.pyfiles of your installed apps
automatically like you can do with the admin autodiscover. Do so by runningautofixture.autodiscover()somewhere in the code, preferably in theurls.py.MoreThere is so much more to explore which might be useful to you and your
projects:There are ways to register customAutoFixturesubclasses with models
that are automatically used when callingloadtestdataon the model.More control for related models, even with relations of related models…
(e.g. by usinggenerate_fk=['author','author__user'])Custom constraints that are used to ensure that created models are
valid (e.g.uniqueandunique_togetherconstraints, which are
already handled by default)ContributeYou can find the latest development version ongithub. Get there and fork it,
file bugs or send me nice wishes.To start developing, make sure the test suite passes:virtualenv .env
source .env/bin/activate
pip install -r requirements/tests.txt
python setup.py testNow go, do some coding.Feel free to drop me a message about critiques or feature requests. You can get
in touch with me bymailortwitter.Happy autofixturing!Changelog0.12.1#85: Better examples in README. Thanks to Dan Hitt for the patch.#86: Less deprecation warnings when using django-autofixture on Python
3.5. Thanks to Nick Timkovich for the patch.#87: Closing files properly, so you should see lessResourceWarningswhile using django-autofixture. Thanks to Nick Timkovich for the patch.0.12.0#81: Add support for UUID fields. Thanks to @jungornti for the patch.#77: Fixing a very rare crash in cases when a generated email in theUserFixturealready exists. Thanks to Tien Nguyen for the patch.0.11.0#75: Support for Django 1.9. Thanks to Adam Dobrawy for the patch.#67: If many to many relations are created in a autofixture, we now make sure
that a registered autofixture is used for this if there is any. Thanks to
Andrew Lewisohn for the patch.0.10.1Fixing unique constraint checks for multipleNonevalues. Thanks to
Andrew Lewisohn for the patch. See#66.0.10.0Supporting Django 1.7 style app configs insettings.INSTALLED_APPSwhen auto-importing autofixture definitions withautofixture.autodiscover.Addingautofixture.generators.PositiveDecimalGenerator.0.9.2FixedUserFixturethat generated usernames with more than 30 characters.0.9.1Fixed unique constraint for models that have multiple unique_togethers set.0.9MakeImageGeneratorconsider the given file storage. Thanks to Andrew
Pashkin for the patch.Fixing check for unique constraint during data generation if the field
allows to be nullable. Thanks for Andrew Pashkin for the report and fix.0.8.0Adding support for django’sImageField. Thanks to Visgean Skeloru for
the patch.0.7.0AddingAutoFixture.pre_process_instancemethod.Allow arbitrary keyword arguments forAutoFixture.createmethod.Fixingautofixture.unregisterfunction.FixingUserFixture.post_process_instance.0.6.3Fixing long stated issue with GenericRelation fields. Thanks to StillNewb
for the patch.0.6.2Supporting Django 1.6.0.6.1Fixing issue with models that have a selfreferencing ForeignKey field.
Thanks to Josh Fyne for the patch.0.6.0Addinggenerators.WeightedGeneratorfor propabilistic selection of
values. Thanks to Jonathan Tien for the idea and patch.Supporting model inheritance. Thanks to Josh Fyne for the patch.0.5.0AddingFirstNameGeneratorandLastNameGenerator. Thanks to Jonathan
Tien for the initial patch.Registered Autofixtures are used for models that are created for foreignkeys
and many to many relations. Thanks to Theo Spears for the report.0.4.0Python 3 support! Though we had to drop Python 2.5 support. If you cannot
upgrade to Python 2.6 by yet, please consider using the 0.3.x versions of
django-autofixture.
By the way: by Python 3 support, I mean, that the test suite is running
without any errors. I have not tested yet the library in production for
Python 3. So please test and submit bug reports if you encounter any.0.3.2DateTimeFieldreceive timezone aware datetime objects now. Thanks to
Scott Woodall for the report and patch.Addingstatic_domainparameter toEmailGeneratorto allow the
production of emails that will always have the same domain. Thanks to
mvdwaeter for the initial patch.0.3.1field_valueswere not picked up if there was a default value assigned to
the field. Thanks to sirex for the report.0.3.0Adding better support for subclassingAutoFixturethrough merging of
nestedValuesclasses.Renamed attribute and argumentnone_chanceto better matching nameempty_pfor generators
andnone_pforAutoFixture.Fixed some issues with management command options. Thanks Mikko Hellsing for
his hard work.Fixed issues in unregister(). Thanks Mikko Hellsing for the report.Adding support forFloatField. Thanks to Jyr Gaxiola for the report.0.2.5Fixing issue with--generate-fkoption in management command. Thanks
Mikko Hellsing for thereport and fix.0.2.4UsingAutofixture.Valuesfor defining initial values inAutofixturesubclasses.Making autodiscover more robust. Don’t break if some module can’t be
imported or throws any other exception.0.2.3Fixing bug when aCharFieldwithmax_lengthsmaller than 15 is used.AutoFixture.field_valuesaccepts callables as values.