Running a test that uses live_server after a test that uses transactional_db causes database errors #1197

Activity

1. m-reichle commented on May 9, 2025

   

   m-reichle

   on May 9, 2025

   Author

   More actions

   I've narrowed this down to the following factors:

   • use Debian Trixie (python 3.13, sqlite 3.46)
   • use an sqlite in-memory database
   • first run a test that uses the transactional_db fixture
   • then run a test that uses the live_server fixture and fires a lot of request from the get-go (in my case an HTMX based view that gets assembled from several components)

   Doing this will result in a corrupted database for the second test.

   My hypothesis would be that something in the extra code that is run for in-memory databases fails with that version of sqlite, but I cannot say for sure. I've switched my tests to using a file-based database as a work-around.
2. suspiciousRaccoon commented on Jul 21, 2025

   

   suspiciousRaccoon

   on Jul 21, 2025

   More actions

   I've found similar problems when using live_server along with playwright's page fixture.

   @pytest.fixture()
   def test_server(page: Page, live_server: LiveServer):
       page.goto(live_server.url)
       return page, live_server

   When using this fixture what I've noticed is that database entries between tests don't get cleaned up, even if I'm not using any of the special options like --reuse-db which means that transactions aren't being rolled back correctly.

   Unsure if it matters, but for playwright to run I have to set:

   os.environ.setdefault("DJANGO_ALLOW_ASYNC_UNSAFE", "true")

   in my conftest.py, even though I'm using the sync api and all my test are sync only.

   I found that in this stackoverflow question.

   I imagine for async tests this would be worse and even more unpredictable.

   If required I could set up a repo with a MCVE of the issue.