使用assertRaises - 处理传播的异常

2 投票
1 回答
1494 浏览
提问于 2025-04-17 10:46

我有一段代码,用来测试一个被包装的异常。当它失败并且异常被抛出时,我觉得错误信息和回溯信息不够详细,主要是因为它没有告诉我预期的结果和实际测试结果之间的区别。我希望能看到异常的详细信息和预期的结果。

我调整了我的测试(见下面的示例代码)。我想知道这种方法是否有效,以及有没有Python的测试或模拟框架可以直接实现这个功能?(目前我在用unittest和mox)

这个问题的一个回答中,简要提到了在这种情况下使用self.fail的合适性,但没有详细说明。我的假设是,如果我试图将测试限制在一个特定的区域,我可以让测试失败。

注意:如果你运行下面的代码示例,它应该会失败,以展示我想看到的行为。我使用的是Python 2.7,Mox 0.5.3。

import sys
import urllib2
from contextlib import closing

try:
    import lxml.etree as ET
except ImportError:
    import xml.etree.ElementTree as ET


class Defect(Exception):
    """Wrapped exception, for module error detection"""
    def __init__(self, *args):
        Exception.__init__(self, *args)
        self.wrapped_exc = sys.exc_info()


class StudioResources:
    """Dummy class"""
    def _opener(self, request, html=False):
        with closing(urllib2.urlopen(request)) as response:
            try:
                if html:
                    import lxml.html
                    return lxml.html.parse(response)
                else:
                    return ET.parse(response)
            except urllib2.HTTPError, e:
                if e.code in [400, 500]: # Bad Request, Internal Server Error
                    raise Defect, "report error to the library maintainer"
                else:
                    raise


###
# Tests
###
import unittest
import mox
import traceback
import difflib
import urllib
import httplib


def format_expectation(exc_expected=None, exc_instance=None):
    """Synopsis - For exceptions, inspired by _AssertRaisesContext

    try:
        self.assertRaises(myexc, self.studio._opener, None)
    except Exception, e:
        self.fail(format_expectation(exc_expected=myexc, exc_instance=e))
    """
    if not isinstance(exc_expected, type) or exc_instance is None:
        raise ValueError, "check __init__ args"

    differ = difflib.Differ()
    inst_class = exc_instance.__class__
    def fullname(c): return "%s.%s" % (c.__module__, c.__name__)
    diff = differ.compare(
        (fullname(inst_class),), (fullname(exc_expected),))
    _str = ("Unexpected Exception type.  unexpected:-  expected:+\n%s"
        % ("\n".join(diff),))
    return _str


class StudioTest(mox.MoxTestBase):
    def setUp(self):
        mox.MoxTestBase.setUp(self)
        self.studio = StudioResources()

    def test_opener_defect(self):
        f = urllib.addinfourl(urllib2.StringIO('dummy'), None, None)
        RESP_CODE = 501
        self.mox.StubOutWithMock(f, 'read')
        self.mox.StubOutWithMock(urllib2, 'urlopen')
        urllib2.urlopen(mox.IgnoreArg()).AndReturn(f)
        f.read(mox.IgnoreArg()).AndRaise(urllib2.HTTPError(
            'http://c.com', RESP_CODE, httplib.responses[RESP_CODE], "", None))
        self.mox.ReplayAll()
        try:
            with self.assertRaises(Defect) as exc_info:
                self.studio._opener(None)
        except Exception, e:
            traceback.print_exc()
            self.fail(format_expectation(exc_expected=Defect, exc_instance=e))
        # check the response code
        exc, inst, tb = exc_info.exception.wrapped_exc
        self.assertEquals(inst.code, RESP_CODE)
        self.mox.VerifyAll()


if __name__ == '__main__':
    unittest.main()

1 个回答

1

在写单元测试的时候,最好把测试的内容限制在一个点上。我觉得你的代码没有什么问题,但我会把整个代码放在一个上下文管理器里。我使用的是nose,而不是unittest,因为nose会把任何AssertionError都当作失败(这意味着你不需要调用self.fail()),我还写了一个自己的上下文管理器来处理这种情况。如果你感兴趣的话,这里有代码:

class assert_raises:

    def __init__(self, exception):
        self.exception = exception

    def __enter__(self):
        return self

    def __exit__(self, exc_type, exc_val, exc_tb):
        assert exc_type is self.exception, "Got '{}', expected '{}'"\
            .format('None' if exc_type is None else exc_type.__name__,
                    self.exception.__name__)
        return True

然后可以像下面这些例子一样使用它:

>>> with assert_raised(ValueError):
...    raise ValueError

>>> with assert_raised(ValueError):
...    pass
Traceback (most recent call last):
    ...
AssertionError: Got 'None', expected 'ValueError'

>>> with assert_raised(ValueError):
...     raise TypeError
Traceback (most recent call last):
    ...
AssertionError: Got 'TypeError', expected 'ValueError'

因为抛出了一个AssertionError,所以nose会把它视为失败,并且会打印出完整的错误追踪信息。这个是为nose设计的,但如果你想用unittest和mox的话,调整一下也很简单。如果你不太在意失败的具体方式,甚至可以直接使用它。

撰写回答