During tests parse fixtures using setUpClass

[Alex Gaynor]

Now that we can do class level setup we should move most of the stuff (but particularly parsing of fixtures) into setUpClass.

[Alex Gaynor]

Patch implements the outlines strategy, 25% gain on admin_views, negligible of the full test run. 6 failing tests.

[Alex Gaynor]

Wontfixing on the grounds that it's non-trivial and the observed gain is tiny.

[for_d]

I have a use case where I have a bunch of tests that never modify the data created in setUp(). They are also very heavy because they use a search index which is built from the database data. I would like to use setUpClass() to set up my test data and do the indexing updating, and tearDownClass() to wipe it. Fixtures in this case do not get loaded, as implied by the bug summary. I don't know if this is a sufficiently compelling case. The unittest module docs seem to imply that class and module fixtures aren't very bad.

[Paul Garner]

It seems a shame this was marked 'wontfix' on the basis that it makes minimal difference to Django's own test suite... this would be useful for framework users' own test suites

[Tim Graham]

In Django 1.8 this is ​fixed in TestCase by d89f56dc4d03f6bf6602536b8b62602ec0d46d2f.