Question

我在虚拟环境中进行了设置：

一切正常，唯一的问题是在运行测试期间。每次django在运行测试函数后尝试刷新数据库时都会抛出错误：

Traceback (most recent call last):
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/test/testcases.py", line 187, in __call__
    self._post_teardown()
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/test/testcases.py", line 796, in _post_teardown
    self._fixture_teardown()
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/test/testcases.py", line 889, in _fixture_teardown
    return super(TestCase, self)._fixture_teardown()
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/test/testcases.py", line 817, in _fixture_teardown
    inhibit_post_syncdb=self.available_apps is not None)
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 159, in call_command
    return klass.execute(*args, **defaults)
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/core/management/base.py", line 415, in handle
    return self.handle_noargs(**options)
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/core/management/commands/flush.py", line 79, in handle_noargs
    six.reraise(CommandError, CommandError(new_msg), sys.exc_info()[2])
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/core/management/commands/flush.py", line 67, in handle_noargs
    savepoint=connection.features.can_rollback_ddl):
  File "/home/lehins/.virtualenvs/studentpal/local/lib/python2.7/site-packages/django/db/transaction.py", line 251, in __enter__
    "The outermost 'atomic' block cannot use "
CommandError: Database test_dev_db 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: The outermost 'atomic' block cannot use savepoint = False when autocommit is off.

因此，对于每个测试用例，我都有一个传递或失败，就像它想象的那样，但我也遇到了这个恼人的错误。

我确实运行了django-admin.py sqlflush --settings=dev_settings --pythonpath=.，这样可以很好地刷新我的开发数据库，没有错误。

在几个测试函数中，我检查了从数据库中提取的几个模型，它似乎正在刷新并重新创建对象，这就是为什么它不会影响实际的测试用例。

我经历了整个追溯，我有点理解为什么会发生，但我无法弄清楚如何处理。任何帮助表示赞赏。

修改

刚刚尝试使用Django-nonrel-1.5运行测试，没有问题。这似乎是1.6版本中的一个错误。

Answer 1

使用SimpleTestCase或自定义TestCase

class CustomTestCase(TestCase):

    def _fixture_teardown(self):
        for db_name in self._databases_names(include_mirrors=False):
            call_command('custom_flush', verbosity=0, interactive=False,
                         database=db_name, skip_validation=True,
                         reset_sequences=False,
                         allow_cascade=self.available_apps is not None,
                         inhibit_post_syncdb=self.available_apps is not None)

由于问题transaction.atomic中的问题flush，您可能需要编写自己的flush。

运行测试时出现Django-nonrel + MongoDB错误

1 个答案: