Menu
I'm creating a Django library which uses optimistic concurrency control to prevent concurrent writes from causing inconsistent data. I'd like to be able to write unit tests for this functionality but I'm not sure how to accomplish this.
I know that Django's unit tests are single threaded, so the only way I can envision a test working is by having two separate database connections (to the same database) open simultaneously and toggling which connection the Django ORM uses when executing queries, though I'm not sure if connection toggling is even possible in Django.
What are some techniques for testing concurrent database operations with Django?
227
The request factory The RequestFactory shares the same API as the test client. However, instead of behaving like a browser, the RequestFactory provides a way to generate a request instance that can be used as the first argument to any view.
Writing testsDjango's unit tests use a Python standard library module: unittest . This module defines tests using a class-based approach. When you run your tests, the default behavior of the test utility is to find all the test cases (that is, subclasses of unittest.
from the docs: When using SQLite, the tests will use an in-memory database by default (i.e., the database will be created in memory, bypassing the filesystem entirely!). The TEST dictionary in DATABASES offers a number of settings to configure your test database.
One way to handle this is to spawn multiple copies of Django runserver in separate processes pointed at the same DB. Then your unit test spawns threads/processes and they all bang on the runservers exercising your concurrency. During teardown you join with all your processes.
126
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
