I have a project using South for DB migrations, and have also installed django-test-utils.
However while ./manage.py test works fine, ./manage quicktest doesn't - I get an error:
Error: Database test_livetalkback couldn't be flushed. Possible reasons:
* The database isn't running or isn't configured correctly.
* At least one of the expected database tables doesn't exist.
* The SQL was invalid.
Hint: Look at the output of 'django-admin.py sqlflush'. That's the SQL this command wasn't able to run.
The full error: (1146, "Table 'test_livetalkback.polls_event' doesn't exist")
This is prefixed with the standard syncdb output.
From the looks of it, what's happening is that ./manage.py test is managing to get to a syncdb that is the original (django-stock) version, whereas quicktest is picking up the South modified version.
I have a project using South for DB migrations, and have also installed django-test-utils.
However while ./manage.py test works fine, ./manage quicktest doesn't - I get an error:
Error: Database test_livetalkback couldn't be flushed. Possible reasons: * The database isn't running or isn't configured correctly. * At least one of the expected database tables doesn't exist. * The SQL was invalid. Hint: Look at the output of 'django-admin.py sqlflush'. That's the SQL this command wasn't able to run. The full error: (1146, "Table 'test_livetalkback.polls_event' doesn't exist")This is prefixed with the standard syncdb output.
From the looks of it, what's happening is that ./manage.py test is managing to get to a syncdb that is the original (django-stock) version, whereas quicktest is picking up the South modified version.