DDF Extras

Debugging

Print model instance values: P

Print all field values of an instance. You can also pass a list of instances or a QuerySet. It is useful for debug:

from django_dynamic_fixture import G, P

P(G(Model))
P(G(Model, n=2))
P(Model.objects.all())

# This will print some thing like that:
# :: Model my_app.MyModel (12345)
# id: 12345
# field_x: 'abc'
# field_y: 1
# field_z: 1

DDF compatibility checking (New in 3.0.0)

Before starting using DDF in your application, it is good to check its compatibility with your application models.

DDF has a simple script that will look for all Django models of all installed Django applications and it will print a report for you:

from ddf import ddf_check_models
succeeded, errors = ddf_check_models()

You can also print in CSV format (using Tabs for separators):

succeeded, errors = ddf_check_models(print_csv=True)

Or even save the report directly to a CSV file:

succeeded, errors = ddf_check_models(csv_filename='ddf_compatibility_report.csv')

Check for a ddf_compatibility_report.csv file in the current directory, so you can use it better in a CSV editor.

Debug Mode (New in 1.6.2)

Print debug log of DDF.

In settings.py:

DDF_DEBUG_MODE = True # default = False

In the test file:

G(MyModel, debug_mode=True)

DDF Version (New in 3.0.2)

Type:

import ddf
ddf.__version__

List of Exceptions

• UnsupportedFieldError: DynamicFixture does not support this field.
• InvalidConfigurationError: The specified configuration for the field can not be applied or it is bugged.
• InvalidManyToManyConfigurationError: M2M attribute configuration must be a number or a list of DynamicFixture or model instances.
• BadDataError: The data passed to a field has some problem (not unique or invalid) or a required attribute is in ignore list.
• InvalidCopierExpressionError: The specified expression used in a Copier is invalid.
• InvalidModelError: Invalid Model: The class is not a model or it is abstract.

Decorators (New in 1.4.0)

Example:

from django_dynamic_fixture.decorators import skip_for_database, only_for_database, SQLITE3, POSTGRES

@skip_for_database(SQLITE3)
def test_some_feature_that_use_raw_sql_not_supported_by_sqlite(self): pass

@only_for_database(POSTGRES)
def test_some_feature_that_use_raw_sql_specific_to_my_production_database(self): pass

It is possible to pass a custom string as argument, one that would be defined in settings.DATABASES[‘default’][‘ENGINE’]:

@skip_for_database('my custom driver')
@only_for_database('my custom driver')

Validation

Validate Models (New in 1.5.0)

This option is a flag to determine if the method full_clean of model instances will be called before DDF calls the save method.

In settings.py:

DDF_VALIDATE_MODELS = False

In the test file:

G(MyModel, validate_models=True)

Signals PRE_SAVE and POST_SAVE:

In very special cases a signal may facilitate implementing tests with DDF, but Django signals may not be satisfactory for testing purposes because the developer does not have control of the execution order of the receivers. For this reason, DDF provides its own signals. It is possible to have only one receiver for each model, to avoid anti-patterns:

from django_dynamic_fixture import PRE_SAVE, POST_SAVE
def callback_function(instance):
    pass # do something
PRE_SAVE(MyModel, callback_function)
POST_SAVE(MyModel, callback_function)