skip to navigation
skip to content

factory_boy 2.6.0

A versatile test fixtures replacement based on thoughtbot's factory_girl for Ruby.


.. image::
:alt: Latest Version

.. image::
:alt: Supported Python versions

.. image::
:alt: Wheel status

.. image::

factory_boy is a fixtures replacement based on thoughtbot's `factory_girl <http:"" thoughtbot="" factory_girl="">`_.

As a fixtures replacement tool, it aims to replace static, hard to maintain fixtures
with easy-to-use factories for complex object.

Instead of building an exhaustive test setup with every possible combination of corner cases,
``factory_boy`` allows you to use objects customized for the current test,
while only declaring the test-specific fields:

.. code-block:: python

class FooTests(unittest.TestCase):

def test_with_factory_boy(self):
# We need a 200€, paid order, shipping to australia, for a VIP customer
order = OrderFactory(
# Run the tests here

def test_without_factory_boy(self):
address = Address(
street="42 fubar street",
customer = Customer(
# etc.

factory_boy is designed to work well with various ORMs (Django, Mogo, SQLAlchemy),
and can easily be extended for other libraries.

Its main features include:

- Straightforward declarative syntax
- Chaining factory calls while retaining the global context
- Support for multiple build strategies (saved/unsaved instances, stubbed objects)
- Multiple factories per class support, including inheritance


* Documentation:
* Repository:
* Package:

factory_boy supports Python 2.6, 2.7, 3.2 and 3.3, as well as PyPy; it requires only the standard Python library.



.. code-block:: sh

$ pip install factory_boy


.. code-block:: sh

$ git clone git://
$ python install


.. note:: This section provides a quick summary of factory_boy features.
A more detailed listing is available in the full documentation.

Defining factories

Factories declare a set of attributes used to instantiate an object.
The class of the object must be defined in the ``model`` field of a ``class Meta:`` attribute:

.. code-block:: python

import factory
from . import models

class UserFactory(factory.Factory):
class Meta:
model = models.User

first_name = 'John'
last_name = 'Doe'
admin = False

# Another, different, factory for the same object
class AdminFactory(factory.Factory):
class Meta:
model = models.User

first_name = 'Admin'
last_name = 'User'
admin = True

Using factories

factory_boy supports several different build strategies: build, create, and stub:

.. code-block:: python

# Returns a User instance that's not saved
user =

# Returns a saved User instance
user = UserFactory.create()

# Returns a stub object (just a bunch of attributes)
obj = UserFactory.stub()

You can use the Factory class as a shortcut for the default build strategy:

.. code-block:: python

# Same as UserFactory.create()
user = UserFactory()

No matter which strategy is used, it's possible to override the defined attributes by passing keyword arguments:

.. code-block:: pycon

# Build a User instance and override first_name
>>> user ='Joe')
>>> user.first_name

It is also possible to create a bunch of objects in a single call:

.. code-block:: pycon

>>> users = UserFactory.build_batch(10, first_name="Joe")
>>> len(users)
>>> [user.first_name for user in users]
["Joe", "Joe", "Joe", "Joe", "Joe", "Joe", "Joe", "Joe", "Joe", "Joe"]

Realistic, random values

Tests look better with random yet realistic values.
For this, factory_boy relies on the excellent `fake-factory <https:"" pypi="" fake-factory="">`_ library:

.. code-block:: python

class RandomUserFactory(factory.Factory):
class Meta:
model = models.User

first_name = factory.Faker('first_name')
last_name = factory.Faker('last_name')

.. code-block:: pycon

>>> UserFactory()
<user: lucy="" murray="">

Lazy Attributes

Most factory attributes can be added using static values that are evaluated when the factory is defined,
but some attributes (such as fields whose value is computed from other elements)
will need values assigned each time an instance is generated.

These "lazy" attributes can be added as follows:

.. code-block:: python

class UserFactory(factory.Factory):
class Meta:
model = models.User

first_name = 'Joe'
last_name = 'Blow'
email = factory.LazyAttribute(lambda a: '{0}.{1}'.format(a.first_name, a.last_name).lower())

.. code-block:: pycon

>>> UserFactory().email


Unique values in a specific format (for example, e-mail addresses) can be generated using sequences. Sequences are defined by using ``Sequence`` or the decorator ``sequence``:

.. code-block:: python

class UserFactory(factory.Factory):
class Meta:
model = models.User

email = factory.Sequence(lambda n: 'person{0}'.format(n))

>>> UserFactory().email
>>> UserFactory().email


Some objects have a complex field, that should itself be defined from a dedicated factories.
This is handled by the ``SubFactory`` helper:

.. code-block:: python

class PostFactory(factory.Factory):
class Meta:
model = models.Post

author = factory.SubFactory(UserFactory)

The associated object's strategy will be used:

.. code-block:: python

# Builds and saves a User and a Post
>>> post = PostFactory()
>>> is None # Post has been 'saved'
>>> is None # has been saved

# Builds but does not save a User, and then builds but does not save a Post
>>> post =
>>> is None
>>> is None

Debugging factory_boy

Debugging factory_boy can be rather complex due to the long chains of calls.
Detailed logging is available through the ``factory`` logger.

A helper, `factory.debug()`, is available to ease debugging:

.. code-block:: python

with factory.debug():
obj = TestModel2Factory()

import logging
logger = logging.getLogger('factory')

This will yield messages similar to those (artificial indentation):

.. code-block:: ini

BaseFactory: Preparing tests.test_using.TestModel2Factory(extra={})
LazyStub: Computing values for tests.test_using.TestModel2Factory(two=<ordereddeclarationwrapper for="" <factory.declarations.subfactory="" object="" at="" 0x1e15610="">>)
SubFactory: Instantiating tests.test_using.TestModelFactory(__containers=(<lazystub for="" tests.test_using.testmodel2factory="">,), one=4), create=True
BaseFactory: Preparing tests.test_using.TestModelFactory(extra={'__containers': (<lazystub for="" tests.test_using.testmodel2factory="">,), 'one': 4})
LazyStub: Computing values for tests.test_using.TestModelFactory(one=4)
LazyStub: Computed values, got tests.test_using.TestModelFactory(one=4)
BaseFactory: Generating tests.test_using.TestModelFactory(one=4)
LazyStub: Computed values, got tests.test_using.TestModel2Factory(two=<tests.test_using.testmodel object="" at="" 0x1e15410="">)
BaseFactory: Generating tests.test_using.TestModel2Factory(two=<tests.test_using.testmodel object="" at="" 0x1e15410="">)

ORM Support

factory_boy has specific support for a few ORMs, through specific ``factory.Factory`` subclasses:

* Django, with ``factory.django.DjangoModelFactory``
* Mogo, with ``factory.mogo.MogoFactory``
* MongoEngine, with ``factory.mongoengine.MongoEngineFactory``
* SQLAlchemy, with ``factory.alchemy.SQLAlchemyModelFactory``


factory_boy is distributed under the MIT License.

Issues should be opened through `GitHub Issues <http:"" rbarrois="" factory_boy="" issues=""/>`_; whenever possible, a pull request should be included.

All pull request should pass the test suite, which can be launched simply with:

.. code-block:: sh

$ make test

In order to test coverage, please use:

.. code-block:: sh

$ make coverage

To test with a specific framework version, you may use:

.. code-block:: sh

$ make DJANGO=1.7 test

Valid options are:

* ``DJANGO`` for ``Django``
* ``MONGOENGINE`` for ``mongoengine``
* ``ALCHEMY`` for ``SQLAlchemy``

Contents, indices and tables

.. toctree::
:maxdepth: 2


* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`

File Type Py Version Uploaded on Size
factory_boy-2.6.0-py2.py3-none-any.whl (md5) Python Wheel 3.4 2015-10-20 35KB
factory_boy-2.6.0.tar.gz (md5) Source 2015-10-20 84KB
  • Downloads (All Versions):
  • 5153 downloads in the last day
  • 23346 downloads in the last week
  • 115563 downloads in the last month