Confusing before/after methods. about django-test-migrations HOT 9 CLOSED

Perhaps initial_migration and tested_migration? The goal here is to set a state, do some prep work, and then test a migration.

from django-test-migrations.

what do you think about: apply_initial_migrations(targets) and apply_tested_migrations(targets)?

from django-test-migrations.

Hm 🤔

from django-test-migrations.

I was confused too.
I thought that before are applying all migrations but the specified one. Because it says generate a state before the actual migration happens.
So if we have migrations 0001, 0002, 0003 then I thought before(('app', '003')) would apply only 0001 and 0002 but actually it includes 0003.
Maybe we need the better clarification about it in documentation?

from django-test-migrations.

Yes, we must update confusing parts!

@wwarne do you want to help with a PR? What parts were the most confusing?

from django-test-migrations.

@sobolevn Yes, I would love to.

The most confusing was that in my mind migrator.before(('main_app', '0004')) had to create the state before the migration named 0004. I was expecting the .before method to behave like a range function. And in reality migration 0004 is included and applied too.

After failing my tests I read examples again and understood that I should use
migrator.before(('main_app', '0003')) (
some preparations
migrator.after(('main_app', '0004'))
some checks

I will try to come up with the suggestion about changing the documentation. Right now I'm not sure how to describe before and action methods short and clearly.

from django-test-migrations.

Ok, today I got confused myself. Spent 20 minutes debugging ArrayField from django. But I have after / before misuse.

I need to refactor it in the future versions.

from django-test-migrations.

I like this naming, @shaleh! 👍

PRs are welcome!

from django-test-migrations.

Yes, I like this one more. Because it has a verb in it.

from django-test-migrations.