WIP: Add test to check whether a migration can be created

[Andrew-Chen-Wang]

Fixes #1054

Description of the Change

Adds a test case to see if a Django version creates a new migration. If it does, decide whether we incorporate the change into the package itself or to simply exclude the Django version that created this regression.

I completely forgot this isn't a Django project, it's a package :)

Checklist

• PR only contains one change (considered splitting up PR)
• unit-test added
• documentation updated
• CHANGELOG.md updated (only for user relevant changes)
• author name in AUTHORS

[Andrew-Chen-Wang]

Interestingly enough, I can't actually seem to produce the error in test cases:

    def test_makemigrations(self):
        try:
            call_command("makemigrations", "oauth2_provider", "--check", "--noinput", "--dry-run")
        except SystemExit:
            self.fail("Migration should be created or there is a regression in Django")
        try:
            with self.settings(AUTH_USER_MODEL="auth.User"):
                call_command("makemigrations", "oauth2_provider", "--check", "--noinput", "--dry-run")
        except SystemExit:
            self.fail("Migration should be created or there is a regression in Django")

Run:

tox -e py39-dj40 tests/test_models.py

Output:

tests/test_models.py ...No changes detected in app 'oauth2_provider'
No changes detected in app 'oauth2_provider'
..............^X.......^CERROR: got KeyboardInterrupt signal

[n2ygk]

I don't think you can exec a check migrations command because the database context for tests is an in-memory database create just for the test cases to use.

[n2ygk]

Closing this as no longer needed