| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
The ad hoc specification of fixtures has been an ongoing source
of bugs in the tests. The straw that broke the camel’s back is
that 7c6eb09 requires the fixtures to be loaded in order (i.e.
children before their parents), and it would have been a painful
process to reorder all the dozens of different fixture lists,
but the test system ought to be more reliable this way.
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously there was just one raw email, and the test code relied
on that fact. Generalise it to handle multiple raw emails.
This change causes a number of tests to fail, because it exposes
failures that should have happened when the second raw email was
added but were masked by the fact that the text of this second
raw email was never loaded. These failures will be fixed in the
next commit.
|
| |
|
|
|
| |
...by forcing the IncomingMessage to be re-parsed after we have
edited it.
|
| | |
|
| | |
|
| |
|
|
| |
dependency on existence of text_binary field in raw_emails model, rewrite tests (and their fixtures) to explicitly load data from FS when raw_emails are used.
|
| |
|
|
| |
don't need to remember to run it everywhere that the raw_emails fixture is used. At the same time, correct the migration that previously removed the data_binary column, as this is assumed for fixture loading. In a future iteration, we should probably stop abusing fixtures like this...
|
| |
|
|
|
|
| |
be in the database (we never write to them, for example), and they bloat it unecessarily, making backups etc difficult.
NOTE: this migration could take a *very* long time.
|
| |
|
|
| |
:public_bodies fixture is, because the PublicBody objects do not work as expected without it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
text.
Does it gradually, so existing column is left alone to speed things up.
|
| |
|
