The problem might be that initial data is loaded after each database
flush, but the same isn't true for migrations. If we want to have RunSQL
as a complete replacement for initial data, then we need to have some
way to mark data loading "migrations" to be loaded after each database
flush. Of course, then some migrations aren't actually migrations...
Another approach is to recommend using fixtures instead of initial data.
- Anssi
On 04/17/2014 11:42 PM, Andrew Godwin wrote:
Hi Christian,
Can you explain your situation more, and perhaps give us some example
files or console output? When you run tests they should run through
all the migrations first, so any initial data should get loaded in
before tests begin.
Andrew
On Thu, Apr 17, 2014 at 1:16 PM, Christian Schmitt
<c.schm...@briefdomain.de <mailto:c.schm...@briefdomain.de>> wrote:
Hello,
currently I try to make a TestSuite for a already grown
application and it is horrible to do so.
But thats not why I'm writing here.
Our Application has some data migrations, previously we used
South, now we use the Django 1.7 Migrations with RunPython to do so.
In the Docs there is also a Article how to do it:
https://docs.djangoproject.com/en/dev/topics/migrations/#data-migrations
Currently If you load initial data with a RunPython command that
your App Depends on (there are some cases, not many, but some) you
will fail hard.
Your Unittests starting to fail. And that is not good, so i think
we should either change something on the Test Suites or we should
make it clear that Data Migrations for initial data is a bad idea
or maybe warn about the drawbacks with Test Cases.
I'm really new to testing and I really needed to figure out whats
going on first until I realized that this behavior comes from the
TestSuite.
--
You received this message because you are subscribed to the Google
Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to django-developers+unsubscr...@googlegroups.com
<mailto:django-developers+unsubscr...@googlegroups.com>.
To post to this group, send email to
django-developers@googlegroups.com
<mailto:django-developers@googlegroups.com>.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/768969da-8f75-4402-80a5-c30c27c74997%40googlegroups.com
<https://groups.google.com/d/msgid/django-developers/768969da-8f75-4402-80a5-c30c27c74997%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-developers+unsubscr...@googlegroups.com
<mailto:django-developers+unsubscr...@googlegroups.com>.
To post to this group, send email to
django-developers@googlegroups.com
<mailto:django-developers@googlegroups.com>.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAFwN1uqasqm17EKHg1PrL5HbJaE3W2hVn%3DBe3wd45yxKRDR04w%40mail.gmail.com
<https://groups.google.com/d/msgid/django-developers/CAFwN1uqasqm17EKHg1PrL5HbJaE3W2hVn%3DBe3wd45yxKRDR04w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5350D836.3040607%40thl.fi.
For more options, visit https://groups.google.com/d/optout.
