#22487: Moving from initial_data to data migrations stops test data persisting
-----------------------------------+--------------------------
Reporter: andrewgodwin | Owner: andrewgodwin
Type: Uncategorized | Status: new
Component: Testing framework | Version: 1.7-beta-1
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------
Before migrations came along, tests would happily flush the database
before each test so they could restore the data that was previously in
there - initial data could be easily loaded from the initial_data fixture.
Now we're encouraging data migrations to load initial data in - which are
superior in almost every way - there's no easy way to replay that data
back at the moment and so tests just don't see this data. Something needs
to be done to allow initial data to persist across tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/22487>
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/055.0e693c9194c96eb9e057dcc1793d67e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
