#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 | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+---------------------------
As pointed out in [https://code.djangoproject.com/ticket/20483#comment:39
this commment], the fix for #20483 doesn't use the correct set of content
types and permissions, because the database is flushed at the end of the
test case, not at the beginning. That behavior was introduced in #18271.
The goal of this ticket is to find a good compromise between:
- making the state of the database between test cases as deterministic as
possible,
- preserving the optimization of #20483,
- not introducing backwards incompatibilities,
- minimizing the amount of changes — we're after 1.6 alpha.
--
Ticket URL: <https://code.djangoproject.com/ticket/20579>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.d682cf3913425f2a9bd17cdd25049ef0%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
