pytest-dev / pytest-dev/pytest-django
serialized_rollback not working under all circumstances
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
I am using serialized_rollback to retain some data migration between tests that need a database transaction. Unfortunately, things break when, for example, using the page fixture of Playwright or the migrator fixture of django-test-migrations. In those cases, serialized_rollback is ignored, and the data is not rolled back anymore. I am not sure why this exactly happens or how to deal with it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the interaction between serialized_rollback and the Playwright page or django-test-migrations migrator fixture. Trace how those fixtures affect the test database transaction, then verify that data is rolled back after the relevant tests complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, playwright, python
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100