只需要调用函数。如果它引发异常，单元测试框架会将其标记为错误。你可能想要添加一个评论，例如:

sValidPath=AlwaysSuppliesAValidPath()
# Check PathIsNotAValidOne not thrown
MyObject(sValidPath)

编辑以补充评论中的澄清:

Unit tests can have 3 results: Pass, Fail, Error. (Actually more if you count XPass/XFail/Skip...) If you're testing a particular exception is not thrown, and it is thrown, then in theory that should be a Fail. But the code above makes it an Error, which is theoretically "wrong". As a practical matter, with an Error your test runner will probably print the stack trace, which may be useful debugging the failure. With a Fail you probably won't see the stack trace. As a practical matter, with a Fail you can mark the test as "Expected to Fail". With an Error you probably can't do that, although you can mark the test as "skip". As a practical matter, making the test case report an Error requires additional code. Whether the difference between "Error" and "Failure" matters depends on your processes. The way my team uses unit tests, they have to all pass. (Agile programming, with a continuous integration machine that runs all the unit tests). What actually matters to my team is "do all the unit tests pass?" (i.e. "is Jenkins green?"). So for my team, there's no practical difference between "Fail" and "Error". Due to the advantages mentioned above (less code, seeing the stack trace), and the fact that Fail/Error are treated the same by my team, I use this approach. You may have different requirements if you use your unit tests in a different way, especially if your processes treat "fail" and "error" differently, or if you want to be able to mark tests as "expected failure". If you would rather have this test report an Error, use DGH's answer.

我是最初的海报，我接受了DGH的上述答案，而没有首先在代码中使用它。

一旦我使用了它，我意识到它需要做一些调整才能真正做到我需要它做的事情(公平地说，他/她确实说了“或类似的东西!”)。

为了其他人的利益，我认为有必要在这里发布这个调整:

    try:
        a = Application("abcdef", "")
    except pySourceAidExceptions.PathIsNotAValidOne:
        pass
    except:
        self.assertTrue(False)

我在这里试图做的是确保如果尝试实例化一个应用程序对象，使用第二个空间参数pySourceAidExceptions。PathIsNotAValidOne将被引发。

我相信使用上面的代码(主要基于DGH的回答)可以做到这一点。

def run_test(self):
    try:
        myFunc()
    except ExceptionType:
        self.fail("myFunc() raised ExceptionType unexpectedly!")

如果您将一个Exception类传递给assertRaises()，则会提供一个上下文管理器。这可以提高测试的可读性:

# raise exception if Application created with bad data
with self.assertRaises(pySourceAidExceptions.PathIsNotAValidOne):
    application = Application("abcdef", "")

这允许您测试代码中的错误用例。

在本例中，您正在测试将无效参数传递给应用程序构造函数时引发PathIsNotAValidOne。

def _assertNotRaises(self, exception, obj, attr):                                                                                                                              
     try:                                                                                                                                                                       
         result = getattr(obj, attr)                                                                                                                                            
         if hasattr(result, '__call__'):                                                                                                                                        
             result()                                                                                                                                                           
     except Exception as e:                                                                                                                                                     
         if isinstance(e, exception):                                                                                                                                           
            raise AssertionError('{}.{} raises {}.'.format(obj, attr, exception)) 

如果需要接受参数，可以修改。

叫喜欢

self._assertNotRaises(IndexError, array, 'sort')

确保对象被初始化而没有任何错误的一种直接方法是测试对象的类型实例。

这里有一个例子:

p = SomeClass(param1=_param1_value)
self.assertTrue(isinstance(p, SomeClass))