Since version 1.7, Django creates migrations for more than just changes to
your model fields. It’s easy to forget to create a migration after changing,
say, the verbose_name_plural of a model class - I’ve done this many times.
This can lead to a mess down the line when multiple developers all end up
creating the same migration in separate branches.
You can avoid this situation by checking for missing migrations in your test
Here we call the makemigrations command in “dry-run” mode and test the
exit code to determine if there are any missing migrations. If there are missing
migrations, the test will fail and print the captured output from the