# Unittest Problems

1. You can see production data when you run the unittests. See the "note" in [this section](https://docs.djangoproject.com/en/3.2/topics/testing/overview/#the-test-database) identiyfing this issue as a possible problem.

2. The unittests require PostgreSQL. For example if you configure django to use SQLite you'll get errors like this when you run the tests:

Creating test database for alias 'default'...

<snip>

self = <django.db.backends.sqlite3.base.SQLiteCursorWrapper object at 0x7fa59dbdd820>
query = 'CREATE TABLE "new__core_task" ("state" text NOT NULL, "name" text NOT NULL, "started_at" datetime NULL, "finished_at"... varchar(256)[] NULL, "parent_task_id" char(32) NULL REFERENCES "core_task" ("pulp_id") DEFERRABLE INITIALLY DEFERRED)', params = None

    def execute(self, query, params=None):
        if params is None:
>           return Database.Cursor.execute(self, query)
E           sqlite3.OperationalError: near "[]": syntax error

/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/django/db/backends/sqlite3/base.py:421: OperationalError

3. The unit tests are very low value currently because they mostly come from the plugin template and are duplicated by more robust functional tests anyway.