initial_data gets populated whenever you migrate your database (e.g.
syncdb, reset, etc). These, at least in my opinion, can be see as
default database fixtures that you should be allowed to have an
expectation of their existence. Gven that, we have *test only*
fixtures (not initial_data) that get
Perhaps I'm missing something... initial_data is "test-only", right?
As opposed to other fixtures which should always be loaded? Then why
would the other fixtures rely on the initial_data?
On Aug 18, 4:15 pm, David Cramer wrote:
> We've been working on switching our test suite to use some new "su
We've been working on switching our test suite to use some new "super
fixtures", which are really just global, test-only initial_data style
fixtures. To implement this we attach to the post_syncdb, and set a
runonce-per-db flag (since it seems to be the only available signal),
but we hit some issue
