解决unittest断言失败，后续的断言不执行进阶之重新封装断言

python unintest单元测试框架提供了一整套内置的断言方法。

 　　1. 如果断言失败，则抛出一个AssertionError,并标识该测试为失败状态。

　　　2. 如果成功，则标识该测试为成功状态。

但存在一个缺点，测试用例中含有多个断言时，一个断言失败，抛出异常，后续断言不再继续执行，也就无从知道后面断言结果。如果使用Python+pytest框架，pytest中的pytest-assume 插件，一个可以允许pytest测试用例中执行多个失败的断言的插件（即断言1，断言2，断言3都失败的情况下，三个断言都能被执行。针对unittest无对应自带的方法可以优化断言失败的问题，找了好些文档，没发现比较好的方法，朋友推荐说可以使用subtest方法，资料比较少没找到好的运用方法，以后继续尝试吧，有了会贴上来，现在先来介绍重写unittest断言：

"""
# File       : checkPoint.py
# Time       ：2021/4/20 14:05
# Author     ：DY
# version    ：V1.0.0
# Description：重写unittest断言方法,解决断言失败不再继续执行的问题
"""
import unittest
class CheckPoint(unittest.TestCase):
    def __init__(self,  methodName='runTest'):
        super(CheckPoint, self).__init__(methodName)
        self._testMethodName = methodName
        self.flag = 0
        self.msg = []

    # 基本的布尔断言：要么正确，要么错误的验证
    def checkAssertEqual(self, arg1, arg2, msg=None):
        """    验证arg1=arg2，不等则fail"""
        try:
            self.assertEqual(arg1, arg2, msg)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkAssertNotEqual(self, arg1, arg2, msg=None):
        """    验证arg1 != arg2, 相等则fail"""
        try:
            self.assertNotEqual(arg1, arg2, msg)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkAssertTrue(self, expr, msg=None):
        """验证expr是true，如果为false，则fail"""
        try:
            self.assertTrue(expr, msg)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkAssertFalse(self, expr, msg=None):
        """    验证expr是false，如果为true，则fail"""
        try:
            self.assertFalse(expr, msg)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    # 比较断言：比较两个变量的值
    def checkAssertGreater(self, first, second, msg=None):
        """　验证first > second，否则fail"""
        try:
            self.assertGreater(first, second)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkAssertGreaterEqual(self, first, second, msg=None):
        """验证first >= second，否则fail"""
        try:
            self.assertGreaterEqual(first, second)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkAssertLess(self, first, second, msg=None):
        """验证first < second，否则fail"""
        try:
            self.assertLess(first, second)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkAssertLessEqual(self, first, second, msg=None):
        """验证first <= second，否则fail"""
        try:
            self.assertLessEqual(first, second)
        except Exception as e:
            self.flag += 1
            self.msg.append("\n{}".format(msg))
            print(e)

    def checkTestResult(self):
        """获取用例执行结果，断言flag是否为0，不为0说明测试用例中存在断言失败"""
        return self.assertEqual(self.flag, 0, "{}".format(self.msg))

 测试用例的引用：测试用例继承父类checkPoint，使用封装的测试用例

from util.checkPoint import CheckPoint

class HomePage(CheckPoint):
    def test_001(self):
        self.checkAssertEqual(1, 1, "断言失败")
        self.checkAssertEqual(1, 2, "断言失败")
        self.checkAssertEqual(1, 3, "断言不咋正确")
        self.checkTestResult()
if __name__ == '__main__':
    unittest.main()

执行结果：

1 != 2 : 断言失败
1 != 3 : 断言不咋正确


['\n断言失败', '\n断言不咋正确']
0 != 2

Expected :2
Actual   :0
<Click to see difference>

Traceback (most recent call last):
  File "D:\DmallAutoPyCMSDY\question.py", line 235, in test_001
    self.checkTestResult()
  File "D:\DmallAutoPyCMSDY\util\checkPoint.py", line 167, in checkTestResult
    return self.assertEqual(self.flag, 0, "{}".format(self.msg))
AssertionError: 2 != 0 : ['\n断言失败', '\n断言不咋正确']

用例test_001的第2/3条断言都是失败的，通过执行结果我们可以看出，第2条断言执行失败后，继续执行第3条用例，并且msg把两次断言失败的异常信息都有收集到，所以此方法可行。

码字不易，如有转载请注明出处，感谢~