1、 The difference between unittest framework and pytest framework

1. Use case writing rules

unittest： Provides testcase The test case 、testsuite test suite 、testfixture Test firmware or fixture 、testloader Test loader 、testrunner Test runner . The following rules must be observed ：

（1） Test files must be imported first import unittest

（2） The test class must inherit unittest.TestCase

（3） The test method must be test start

pytest： It is python Third party testing framework for , be based on unittest The extension framework of , The following rules must be observed ：

（1） The test file name must be test_ Beginning or _test ending

（2） Test class commands must start with Test start

（3） The test method must be test start

2. Pre and post use cases

unittest:

setUp/tearDown         Run once before or after each use case

        Open the browser , Load web page / Close page

setUpClass and tearDownClass         Run once before or after each class

        Create database connection , Create a log object / Close database connection , Destroy log object

setUpModule and tearDownModule        Run once before and after each door module

pytest：

Method level ：

setup_mmothod/teardown_mothod        Before and after the method

setup/teardown

Function level ：

setup_function/teardown_function        Before and after the function

Class level ：

setup_class/teardown_class        Before and after the class

Module level ：

setup_module/teardown_module         Before and after the module

also ： You can also add... Before the function @pytest.fixture() Decorator

3. Assertion

unittest：assertTure、assertEqual、assertln

pyutest：assert

4. The report

unittest：htmltestrunner

pytest： plug-in unit ：pytest-HTML,allure

5. Fail to run again

unittest： No,

pytest：pytest-rerunfailures plug-in unit

6. Data driven

unittest：ddt

pytest：@pytest.mark.parametrize Decorator

7. Use case classification execution

unittest： By default, all , It can also be done through testsuite To execute some use cases , perhaps -k Parameters

pytest：@pytest.mark