pytest-django async test doesn't see rows created by a fixture (count is 0, or ForeignKeyViolation on insert) with @pytest.mark.django_db: use @pytest.mark.django_db(transaction=True)
Fix: mark async DB tests with @pytest.mark.django_db(transaction=True) (or request the transactional_db fixture) instead of plain @pytest.mark.django_db.
Repro (Django 5.1.3, pytest-django 4.9.0, pytest-asyncio 0.24.0, asyncio_mode=auto): a sync fixture does Project.objects.create(name='p'), then async def test_x(project): assert await Project.objects.acount() == 1 fails with assert 0 == 1 under django_db, and passes under django_db(transaction=True). On Postgres the same mismatch showed up as psycopg.errors.ForeignKeyViolation when the async code inserted a row pointing at the fixture's object.
Cause (likely): the default django_db wraps the test in a transaction that is never committed, but async ORM calls run on a worker thread with a different DB connection, so they can't see the uncommitted fixture rows. transaction=True commits for real and truncates tables afterwards, so it is slower; only use it on the async tests.
The same applies to Channels consumer tests: without a db mark, connecting a WebsocketCommunicator fails with 'RuntimeError: Database access not allowed, use the "django_db" mark, or the "db" or "transactional_db" fixtures to enable it.' because the consumer closes old DB connections on each message. DRF's APIClient has no async variant; call it via await sync_to_async(client.get)(url) inside async tests.