django-tenants & pytest - Issues with postgres multiple schemas.

[geekashu]

Hi,

I am trying to use pytest with django-tenants which uses PostgreSQL schemas to isolate clients. How do I configure pytest-django so that if I am using TenantTestCase which actually creates a test schema along with public starts to use both the schema's or set the database search path to 'search_path=test, public'.

It seems pytest is only using the public schema and thus fails to find out the test schema.

The models that I want to test gets created in test schema, isolated from public.

I read in the documentation that pytest-django doesn't play well with multiple databases. Is it true with multiple schema's as well which are in a single database?

The tests are running fine with manage.py test (Django inbuilt testing) and utilizing both the schemas.

Thanks.

[shinto-dev]

I am facing the same issue. My pytests are using only public schema. Is there any way to overcome this problem?

[akifd]

This is not pytest-django issue. I personally worked around this by making fixture that creates the tenant and activates it. A simple version would go something like this:

import pytest
from django_tenants.utils import tenant_context


@pytest.fixture
def tenant(db):
    tenant = Tenant(schema_name="test")
    tenant.save(verbosity=0)
    tenant.domains.create(domain="tenant.test.com", read_only=True)

    with tenant_context(tenant):
        yield tenant

    tenant.save()

Then you can create a test like this:

def test_create_user(tenant):
    # Tenant is activated in this test.

[bluetech]

pytest-django does not support using custom TestCases. You can always use the TenantTestCase itself as unittest test and pytest will pick it up as normal.