Change fixture doctests to unit tests

[Eric Holscher]

These have the most amount of flushing, which will slow down real test runs. I've gone ahead and done a good amount of this, it does touch management commands to have a return_output that you can pass into call_command, so it returns instead of prints for dumpdata and such.

[Eric Holscher]

A slightly updated patch.

[Eric Holscher]

Updated to pass around streams for stdout and stderr

[Eric Holscher]

This is a basic patch that makes the tests pass. I'm not totally sold on the changes to the management commands -- feels like that should be using the new logging infrastructure. It should probably have a little bit of a wrapper that we can swap out the explicit stdout calls to logging.

This should probably also be 2 tickets -- but they are interconnected via a little yak shaving :)

[Russell Keith-Magee]

There is one test failure for this patch under MySQL:

======================================================================
FAIL: test_format_discovery (modeltests.fixtures.tests.FixtureTransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/rkm/projects/django/hg/tests/modeltests/fixtures/tests.py", line 262, in test_format_discovery
    '<Article: Python program becomes self aware>'
  File "/Users/rkm/projects/django/live/django/test/testcases.py", line 470, in assertQuerysetEqual
    return self.assertEqual(map(transform, qs), values)
AssertionError: ['<Article: XML identified as leading cause of cancer>', '<Article: Time to reform copyright>', '<Article: Poker on TV is great!>', '<Article: Python program becomes self aware>'] != ['<Article: Time to reform copyright>', '<Article: Poker has no place on ESPN>', '<Article: Python program becomes self aware>']

The test in question was commented out under MySQL under the doctests; it's not immediately clear to me whether this is a test that should still be commented out, or whether the move to TransactionTestCase should overcome that problem and we've just revealed a previously unknown problem.

Also - given that this test introduces the stdout/stderr arguments, it would make sense to port the multiple-databases fixture loading test that currently does some jiggery-pokery to work around stdout handling.

[Russell Keith-Magee]

Updated fix, mostly formatting changes (this time with the missing file)

[Russell Keith-Magee]

(In [13319]) Fixed #13636 -- Migrated fixtures tests to use unittests, eliminating another set of expensive flush calls. Thanks to Eric Holscher for the patch.

[Jacob]

Milestone 1.3 deleted