How to test sync WebsocketConsumer that queries the database about channels HOT 5 OPEN

I created this repository to reproduce the issue https://github.com/jlariza/channels_testing_bug using cookiecutter

To test:

• create a venv using python 3.11
• run pip install -r requirements/local.txt to install dependencies
• create a postgres database called channelstestingbug
• run migrations
• run pytest channels_testing_bug/myapp
• You'll get the django.db.utils.OperationalError: the connection is closed error in channels_testing_bug/myapp/tests.py:20 in create_instance call.
• If you change it to create the model in the setUp call, the error will be raised by channels_testing_bug/myapp/consumers.py:14: when it tries to filter the database.

The consumer works; I already tested it in another project. However, the tests fail because they cannot handle the async connection to the database.

Any ideas of what I'm missing or doing incorrectly?

Thank you,

from channels.

I suspect this is about how pytest manages the connection between tests.

I'd try inclining the model creation in the test case, to see if that makes progress and then adjust out from there.

from channels.

@carltongibson no luck. If you try to run the model creation in the test case directly, it raises django.core.exceptions.SynchronousOnlyOperation but if you use the database_sync_to_asyncdecorator, the OperationalError is raised again.

I tried creating the model using acreate in the testcase but then the OperationalError is raised in this line if MyModel.objects.filter(id=self.object_id).exists(): again.

from channels.

it raises django.core.exceptions.SynchronousOnlyOperation

Yes, you'd need to wrap it in sync_to_async().

The idea is to reduce the number of different context so you can identify when the DB connection is being closed.

from channels.

MyModel.objects.filter(id=self.object_id).exists()

This will be because of the transaction test case usage. From the other transaction the object isn't yet saved, I'd guess.

from channels.