Shulou(Shulou.com)06/02 Report--

This article introduces the difference between python automated testing framework pytest and unittest. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

I. use case design rules

1.unittest

(1) the test class must inherit unittest.TestCase

(2) the test function must start with "test_"

(3) the test class must have a unittest.main () method

2.pytest

(1) the file name of the test file must start with "test_" or end with "_ test"

(2) the name of test class must start with "Test"

(3) the test function name must start with "test"

(4) the "_ _ init__" method cannot be used in the test class

Conclusion: pytest is a new testing framework based on unittest, which is simpler and more efficient than unittest. Pytest is compatible with unittest test cases, but on the other hand, unittest is not compatible with pytest, so pytest is more fault-tolerant! Pytest is more comprehensive than unittest in using interactive logic!

Unittest is the test library that comes with python. If you only know the basics of python and learn the unittest framework, it is easier to understand. Unittest framework can also achieve most of the business tests in the market! It is suggested that you can first understand the unittest framework, and then learn the pytest framework, you can better feel the advantages and disadvantages of the two frameworks.

Second, assertion comparison

1.unittest assertion

AssertEqual (a, b) # judge whether an and b are equal

AssertNotEqual (a, b) # judge that an is not equal to b

AssertTrue (a) # determines whether an is Ture

AssertFalse (a) # determines whether an is False

AssertIn (a, b) # an is included in b

AsserNotIn (a, b) # an is not included in b

……

2.pytest assertion

Pytest only needs to use assert to assert, and assert can be followed by the conditions that need to be asserted, for example: assert a = = b # to determine whether an is equal to b,

Assert a! = b # judge that an is not equal to b, assert an in b # judge that b contains a

Summary: judging from the above assertions, pytest assertions are simpler than unittest assertions. Unittest assertions need to remember a lot of assertion formats. Pytest has only one expression, assert, which is more convenient to use.

Pre-and post-use cases

1.unittest front and rear

(1) execute each use case before execution through setup, and execute after each use case execution in teardown.

(2) all use cases in setupclass class are executed before execution, and all use cases in teardownclass class are executed after execution.

2.pytest front and rear

(1) Module level: setup_module/teardown_module, the entire .py is executed before the start of all use cases / after all use cases are executed

(2) function level: setup_function/teardown_function, which takes effect only at the function level, and is executed once before and after the start of each use case.

(3) Class level: setup_class/teardown_function, which only takes effect at the class level. All use cases in the class are executed once before the start of the class, and once after all use cases are executed.

(4) method level: setup_method/teardown_method, but the method level in the class takes effect. The method is executed consistently before the method starts, and once after the method ends.

(5) method level: setup/teardown, which is similar to setup_method/teardown_method usage, but lower than method level, that is, in the same method, setup_method is executed before setup, and teardown is executed before teardown_method in the end of the method.

The pytest custom settings are pre-and post-set:

Through firture, you can customize the front and post of pytest in the format fixture (scope= "function", params=None, autouse=False, ids=None, name=Noe).

Scope: there are four levels, function (default), class,module,session

Params: parameter list

Autouse:False is the default value, which means that fixture needs to be activated according to the set condition (scope level). If Ture, all function levels are activated fixture.

Ids: a list of id for each string, which doesn't feel very useful.

The name of name:fixture

IV. Parameterization

1.unittest parameterization

Can be implemented through nose_parameterized, format: @ nose_parameterized.parameterized.expand (data), 'data' is parameterized data in list format

2.pytest parameterization

This is achieved through the decorator @ pytest.mark.parametrize

Fifth, the way to generate the report

1.unittest

Generated by HTMLTestRunner

2.pytest

(1) generate report in html format through pytest-html

(2) generate the scheme through allure (very detailed)

On the python automated testing framework pytest and unittest what is the difference to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.