…est database if it exists.
* Added NonIsolatedDatabaseTestCase and NonIsolatedDestructiveDatabaseTestCase, they do clean up (rollback or db flush) only once - after test case end, so test in the case are not isolated considering data in database, but running of tests can be much faster. * Added module level cleanup (by module attribute database_single_transaction and database_flush), so several test cases in module can perform only one cleanup (after all test cases finished), so again, they are not isolated considering data in database, but runnin of tests can be much faster. Also fixtures for module can be added this way. * Fixed DestructiveDatabaseTestCase having database_single_transaction = True which caused errors when testing code which is using commin_unless_managed and catching IntegrityError. Conflicts: djangosanetesting/cases.py
…aving one test not doing database flush in destructivedatabase case).
* Flushes are done only AFTER test with database_flush = True, every test will clean after itself so we don't need to flush at start * Database is not handled when test will be skipped * startTest refactored a bit to more granular methods * Django multi database support is now detected only once at import
…nosetests (see issue #8)
…Django Test Cases