#20579: Define the expected state of the database between test cases
-----------------------------------+-------------------------------------
Reporter: aaugustin | Owner: aaugustin
Type: Bug | Status: new
Component: Testing framework | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+-------------------------------------
Comment (by aaugustin):
This proposal for test case reordering still assumes that all
TransactionTestCase define available_apps. I'm not sure we can provide a
generic solution, and the current code (hack?) looks good enough for
Django's own test suite.
Indeed, our problem is that we want to express "between X and X" in terms
of "before X" and "after X", and we don't have enough context to optimize
things. One possibility would be to add a global variable to track
information about the state of the database, so the next test case could
know what the previous did. Still, as long as we try to maintain strict
backwards compatibility, there's no silver bullet.
--
Ticket URL: <https://code.djangoproject.com/ticket/20579#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.559a6e1c5bbe8803147d5c8f494c12e8%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
