integration with factory-boy or other similar solution about django-test-migrations HOT 7 CLOSED

Thanks a lot for the suggestion! However, I think that data creation is out of scope of this project.
Currently I don't have any problems creating it with a code like this:

@pytest.mark.django_db
def test_my_app_migration0031(migrator, fakery):
    """Ensures that the some fields are deleted correctly."""
    old_state = migrator.before(
        ('my_app', '0030_pre'),
    )
    my_model = old_state.apps.get_model(
        'my_app', 'MyModel',
    )

    kwargs_to_delete = [
        {'a': None},
        {'b': 'in_progress'},
        {'c': None},
        {'d': ''},
        {'e': ''},
        {'f': None},
    ]

    for kwargs in kwargs_to_delete:
        fakery.m(my_model)(**kwargs)

    assert my_model.objects.count() == len(kwargs_to_delete)

    new_state = migrator.after(('my_app', '0031_some'))
    my_model = new_state.apps.get_model(
        'my_app', 'MyModel',
    )

    assert not my_model.objects.count()

from django-test-migrations.

What's exactly fakery fixtures?
Is it provided by some pytest plugin or it's implemented by you?

from django-test-migrations.

Oh, sorry. It is a tool similar to factoryboy: https://github.com/fcurella/django-fakery
I use it in all of my projects. It is just awesome!

from django-test-migrations.

Looks really good! I will give it a shot, even just for migrations tests.
I will also do some deeper research on possible ways to integrate factory-boy with our project.

from django-test-migrations.

It seems like using factories would be pretty hard without either duplicating factories for each tested state, or getting a lot of strange errors because factories are always a mirror of the last database state. To me neither of those options seem worth it.

from django-test-migrations.

That's true, it's possible, but implementation and maintenance will be much more complicated than the benefits, so I am closing this issue

from django-test-migrations.

https://github.com/fcurella/django-fakery can be used, because it uses _meta to inspect models in runtime.
You don't have to pre-define anything. So, that's quite useful.

from django-test-migrations.