Django test app error - Got an error creating the test database: permission denied to create database

Checking your Django settings.py

User credentials: are they correct?

In settings.py, verify that your 'DATABASES' configuration, particularly the username and password is precisely the same as the ones set in PostgreSQL. Sometimes, simple typing mistakes can lead to frustrating permission issues.

Naming your Django test database: unique is the way to go

Under 'DATABASES' creating a TEST dictionary with a unique NAME for your test database is always prudent:

'DEFAULT': {
    'ENGINE': 'django.db.backends.postgresql',
    'NAME': 'app_data',
    'TEST': {
        'NAME': 'test_app_data',
        // not recommended to name your database as "best_app_data" 
    },
    ...
}


SQLite: the Django test database "easy button"

Another workaround is to use SQLite as your test database engine by setting it in the TEST dictionary under DATABASES. SQLite accepts any user without additional permission hurdles.

'TEST': {
    'ENGINE': 'django.db.backends.sqlite3',
    'NAME': 'my_test_database',
    // Name it after your ex, since it's light and a breeze to discard post tests ;) 
}


MySQL vs PostgreSQL: Battle of the databases

PostgreSQL not your style, for all the MySQL fans out there

While PostgreSQL uses CREATEDB, MySQL uses a different legislation. You'll grant privileges with:

GRANT ALL PRIVILEGES ON `your_test_database`.* TO 'my_django_user'@'localhost';


Things to remember: Django migrate vs test

Running migrate alters your existing database schema, however, running tests create an entirely new database.

Post-Test cleaning: SQLite therapy

If you're using SQLite for testing, don't forget to clean up the file created post-testing. It's always pleasant to start fresh.

Django testing best practices

Dedicated user for testing: not a bad idea

Having a dedicated database user helps in isolating permission issues and prevents production credentials from getting disturbed.

Keeping tests error-free: it needs a checkup too

Run python manage.py test appname frequently to ensure that both migrations and test commands function smoothly post any database changes or modification to permissions.

Official Django docs: Read 'em

Always consult Django's official documentation when setting up or facing issues with Django tests. After all, there's no guide better than the creator's guide itself!