Python:使用coverage运行nose测试时的AssertionError

Question

我对python测试相当绿色,所以这可能是我做错了.

当我运行我的测试时,测试运行器工作正常并且覆盖范围也很好..但是在两者之间我得到一个断言错误:

Traceback (most recent call last):
  File "/usr/local/bin/coverage", line 9, in <module>
    load_entry_point('coverage==3.5.1', 'console_scripts', 'coverage')()
  File "/usr/local/lib/python2.7/dist-packages/coverage/cmdline.py", line 657, in main
    status = CoverageScript().command_line(argv)
  File "/usr/local/lib/python2.7/dist-packages/coverage/cmdline.py", line 526, in command_line
    self.coverage.stop()
  File "/usr/local/lib/python2.7/dist-packages/coverage/control.py", line 389, in stop
    self.collector.stop()
  File "/usr/local/lib/python2.7/dist-packages/coverage/collector.py", line 262, in stop
    assert self._collectors[-1] is self
AssertionError

为了使事情变得更加困难,我正在尝试测试命令行实用程序.这意味着我必须告诉覆盖范围以涵盖子进程调用.

我认为我已经完成了这部分工作,因为报道现在正在报告正在运行的脚本的覆盖百分比.但是自从我完成覆盖工作后,我无法摆脱AssertionError.

有些人帮助理解真正意义上的错误.我的所有代码都可以在github上找到:

• 回购
• setup.py
• run_tests
• 子进程调用

快速运行:

cd /tmp/ && git clone git://github.com/h3/django-duke-client.git 
cd django-duke-client && chmod a+x run_tests && ./run_tests

谢谢

更新

我在另一台计算机上运行测试,我得到了相同的AssertionError ..加上一个新的TypeError.测试再次正确运行,即使出现这些错误,覆盖范围似乎也能正常运行.

...
Ran 9 tests in 1.324s

OK
Traceback (most recent call last):
  File "/usr/local/bin/coverage", line 9, in <module>
    load_entry_point('coverage==3.5.1', 'console_scripts', 'coverage')()
  File "/usr/local/lib/python2.7/dist-packages/coverage/cmdline.py", line 657, in main
    status = CoverageScript().command_line(argv)
  File "/usr/local/lib/python2.7/dist-packages/coverage/cmdline.py", line 526, in command_line
    self.coverage.stop()
  File "/usr/local/lib/python2.7/dist-packages/coverage/control.py", line 389, in stop
    self.collector.stop()
  File "/usr/local/lib/python2.7/dist-packages/coverage/collector.py", line 262, in stop
    assert self._collectors[-1] is self
AssertionError
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.7/multiprocessing/util.py", line 284, in _exit_function
    info('process shutting down')
TypeError: 'NoneType' object is not callable
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.7/multiprocessing/util.py", line 284, in _exit_function
    info('process shutting down')
TypeError: 'NoneType' object is not callable

Name                               Stmts   Miss Branch BrPart  Cover   Missing
------------------------------------------------------------------------------
dukeclient/__init__                   53     53      2      0     4%   1-93
dukeclient/commands/__init__          41     33      6      2    26%   1-9, 12, 14-15, 17, 24-28, 34-43, 46-63
...

Answer 1

关于NoneType is not callable error，请在下面找到一些可能对您有帮助的元素。

在您的模块中plugintest.py，nose-1.1.2-py2.7.egg/nose/plugins/第 174 行，可以读取以下行：

from multiprocessing import Manager

这导致multiprocessing.util包被导入，并用它来注册退出函数：

atexit.register(_exit_function)

问题似乎是在调用之前multiprocessing.util加载的内容然后被卸载，顺便说一句，它是函数定义。plugintest_exit_function

因此，如果将其导入文件中setup.py：

from multiprocessing import util

错误消失。

顺便说一句，我必须评论测试中失败的某些部分或更改某些代码行：

• 该-m命令似乎无效；
• 我不得不重命名duke_conf.yml为duke_conf.yml;
• README.rst检查文件是否存在的测试LICENSE失败（没有时间检查原因）；

希望能帮助到你，