You may have done unit testing or heard the term unit test, which involves breaking down your code into smaller units and testing them to see if they are producing the correct output.<\/p>\n\n\n\n
Python has a robust unit testing library called unittest<\/a> that provides a comprehensive set of testing features. However, some developers believe that In this article, you’ll look at how to use the Pytest is a third-party library that must be installed in your project environment. In your terminal window, type the following command.<\/p>\n\n\n\n Pytest has been installed in your project environment, and all of its functions and classes are now available for use.<\/p>\n\n\n\n Before getting into what Here’s a Python file To run the above test, simply enter the The above test failed, as evidenced by the output generated by the This occurred because If you’ve used the Assume you want to write a Now, from the command line, run these tests with As you can see, the However, writing those tests requires more lines of code, which include:<\/p>\n\n\n\n However, this is not the case with It’s as simple as that, there’s no need to import the package or use pre-defined assertion methods. With a detailed description, you will get a nicer output.<\/p>\n\n\n\n The following information can be found in the output:<\/p>\n\n\n\n What exactly is parametrization? Parametrization<\/strong> is the process of running multiple sets of tests on the same test function or class, each with a different set of parameters or arguments. This allows you to test the expected results of different input values.<\/p>\n\n\n\n If you want to write multiple tests to evaluate various arguments for the But wait, there’s a twist, Using parametrization, you can eliminate code duplication and significantly reduce your test code.<\/p>\n\n\n\n The Using In testing, a fixture<\/a> provides a defined, reliable, and consistent context for the tests. This could include environment (for example a database configured with known parameters) or content (such as a dataset). Source<\/a><\/p>\n<\/blockquote>\n\n\n\n Here’s an example of when you should use fixtures. Assume you have a continuous stream of dynamic vehicle data and want to write a function To check whether the function works properly, you would write a test that looks like the following:<\/p>\n\n\n\n The test function Following the creation of this function, you will create another test function and repeat the process.<\/p>\n\n\n\n This is analogous to repeatedly writing the same code. To avoid writing the same code multiple times, create a function decorated with As you can see from the code above, the number of lines has been reduced to some extent, and you can now write a few more tests by reusing the Consider the example of creating a database connection, in which a fixture is used to set up the resources and then tear them down.<\/p>\n\n\n\n A fixture This fixture can be passed as an argument to the test function. Assume you want to write a function to insert a value into a database, simply do the following:<\/p>\n\n\n\n The You can now write as many test functions as you want without having to rewrite the database setup code.<\/p>\n\n\n\n Pytest provides a few built-in markers to mark your test functions which can be handy while testing.<\/p>\n\n\n\n In the earlier section, you saw the parametrization of arguments using the If you have a test function that you want to skip during testing for some reason, you can decorate it with In the Both test functions in this script are marked with The report shows that two tests were passed and two were skipped.<\/p>\n\n\n\n If you want to conditionally skip a test function. In that case, use the In this example, two test functions ( You can add warning filters to specific test functions or classes using the Here’s an example of the code from above.<\/p>\n\n\n\n In this example, a warning message is emitted by a helper warning function ( Both test functions ( These test functions call You can see in the summary of the report generated by Pytest provides numerous command-line options that allow you to customize or extend the behavior of test execution. You can list all the available Here are some You can specify which tests to run by following the If you want to run tests that contain The tests that have If you want to run all other tests but not the ones with “test_special” in their names, use the following command.<\/p>\n\n\n\n The expression You can use the following options to customize the output and the report:<\/p>\n\n\n\n Output of the tests with increased verbosity.<\/strong><\/p>\n\n\n\n Output of the tests with decreased verbosity.<\/strong><\/p>\n\n\n\n When you use Using the If you don’t want to collect tests from a specific path or file, use the The When you use the Pytest immediately exits the test execution when it finds a failed test and a stopping message appears in the report summary.<\/p>\n\n\n\n Pytest is a testing framework that allows you to write small and readable tests to test or debug your code.<\/p>\n\n\n\n In this article, you’ve learned:<\/p>\n\n\n\n \ud83c\udfc6Other articles you might be interested in if you liked this one<\/strong><\/p>\n\n\n\n \u2705Debug\/Test your code using the unittest module in Python<\/a>.<\/p>\n\n\n\nunittest<\/code> is more verbose than other testing frameworks.<\/p>\n\n\n\npytest<\/code> library to create small, concise test cases for your code. Throughout the process, you’ll learn about the pytest library’s key features.<\/p>\n\n\n\nInstallation<\/h2>\n\n\n\n
pip install pytest<\/pre><\/div>\n\n\n\n
Getting Started With Pytest<\/h2>\n\n\n\n
pytest<\/code> can do, let’s take a look at how to use it to test the code.<\/p>\n\n\n\ntest_square.py<\/code> that contains a square<\/code> function and a test called test_answer<\/code>.<\/p>\n\n\n\n# test_square.py\n\ndef square(num):\n return num**2\n\ndef test_answer():\n assert square(3) == 10<\/pre><\/div>\n\n\n\n
pytest<\/code> command into your terminal, and the rest will be handled by the pytest<\/code> library.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest\n========================================= test session starts ==========================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 1 item\n\ntest_square.py F [100%]\n\n=============================================== FAILURES ===============================================\n_____________________________________________ test_answer ______________________________________________\n\n def test_answer():\n> assert square(3) == 10\nE assert 9 == 10\nE + where 9 = square(3)\n\ntest_square.py:7: AssertionError\n======================================= short test summary info ========================================\nFAILED test_square.py::test_answer - assert 9 == 10\n========================================== 1 failed in 0.27s ===========================================<\/pre><\/div>\n\n\n\n
pytest<\/code> library. You might be wondering how pytest<\/code> discovered and ran the test when no arguments were passed.<\/p>\n\n\n\npytest<\/code> uses standard test discovery. This includes the conventions that must be followed for testing to be successful.<\/p>\n\n\n\n\n
test<\/code>, as well as test<\/code> prefixed test functions and modules inside Test<\/code> prefixed test classes that do not have a __init__<\/code> method, from these files.<\/li>\n\n\n\nWhy do Most Prefer pytest?<\/h2>\n\n\n\n
unittest<\/code> library before, you’ll know that even writing a small test requires more code than pytest<\/code>. Here’s an example to demonstrate.<\/p>\n\n\n\nunittest<\/code> test suite to test your code.<\/p>\n\n\n\n# test_unittest.py\n\nimport unittest\n\nclass TestWithUnittest(unittest.TestCase):\n def test_query(self):\n sentence = \"Welcome to GeekPython\"\n self.assertTrue(\"P\" in sentence)\n self.assertFalse(\"e\" in sentence)\n\n def test_capitalize(self):\n self.assertEqual(\"geek\".capitalize(), \"Geek\")<\/pre><\/div>\n\n\n\n
unittest<\/code>.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>python -m unittest test_unittest.py\n.F\n======================================================================\nFAIL: test_query (test_unittest.TestWithUnittest)\n----------------------------------------------------------------------\nTraceback (most recent call last):\n File \"D:\\SACHIN\\Pycharm\\pytestt_lib\\test_unittest.py\", line 9, in test_query\n self.assertFalse(\"e\" in sentence)\nAssertionError: True is not false\n\n----------------------------------------------------------------------\nRan 2 tests in 0.001s\n\nFAILED (failures=1)<\/pre><\/div>\n\n\n\n
test_query<\/code> test failed while the test_capitalize<\/code> test passed, as expected by the code.<\/p>\n\n\n\n\n
unittest<\/code> module.<\/li>\n\n\n\nTestWithUnittest<\/code>) is created by subclassing TestCase<\/code>.<\/li>\n\n\n\nassertTrue<\/code>, assertFalse<\/code>, and assertEqual<\/code>).<\/li>\n<\/ul>\n\n\n\npytest<\/code>, if you wrote those tests with pytest<\/code>, they must look like this:<\/p>\n\n\n\n# test_pytest.py\n\ndef test_query():\n sentence = \"Welcome to GeekPython\"\n assert \"P\" in sentence\n assert \"e\" not in sentence\n\n\ndef test_capitalize():\n assert \"geek\".capitalize(), \"Geek\"<\/pre><\/div>\n\n\n\n
D:\\SACHIN\\Pycharm\\pytestt_lib>pytest\n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 2 items\n\ntest_pytest.py F. [100%]\n\n============================================================================ FAILURES ============================================================================ \n___________________________________________________________________________ test_query ___________________________________________________________________________ \n\n def test_query():\n sentence = \"Welcome to GeekPython\"\n assert \"P\" in sentence\n> assert \"e\" not in sentence\nE AssertionError: assert 'e' not in 'Welcome to GeekPython'\nE 'e' is contained here:\nE Welcome to GeekPython\nE ? +\n\ntest_pytest.py:6: AssertionError\n==================================================================== short test summary info ===================================================================== \nFAILED test_pytest.py::test_query - AssertionError: assert 'e' not in 'Welcome to GeekPython'\n================================================================== 1 failed, 1 passed in 0.31s ===================================================================<\/pre><\/div>\n\n\n\n
\n
test_pytest.py<\/code>, was collected.<\/li>\n\n\n\n\"F\"<\/code> and a dot (.<\/code>). An \"F\"<\/code> indicates a failed test<\/strong>, a dot (.<\/code>) indicates a passed test<\/strong>, and a \"E\"<\/code> indicates an unexpected condition that occurred during testing<\/strong>.<\/li>\n\n\n\nParametrize Tests<\/h2>\n\n\n\n
square<\/code> function, your first thought might be to write them as follows:<\/p>\n\n\n\n# Function to return the square of specified number\ndef square(num):\n return num ** 2\n\n# Evaluating square of different numbers\ndef test_square_of_int():\n assert square(5) == 25\n\ndef test_square_of_float():\n assert square(5.2) == 27.04\n\ndef test_square_of_complex_num():\n assert square(5j+5) == 50j\n\ndef test_square_of_string():\n assert square(\"5\") == \"25\"<\/pre><\/div>\n\n\n\n
pytest<\/code> saves you from writing even more boilerplate code. To allow the parametrization of arguments for a test function, pytest<\/code> provides the @pytest.mark.parametrize<\/code> decorator.<\/p>\n\n\n\nimport pytest\n\ndef square(num):\n return num ** 2\n\n@pytest.mark.parametrize(\"num, expected\", [\n (5, 25),\n (5.2, 27.04),\n (5j + 5, 50j),\n (\"5\", \"25\")\n])\ndef test_square(num, expected):\n assert square(num) == expected<\/pre><\/div>\n\n\n\n
@pytest.mark.parametrize<\/code> decorator defines four different (\"num, expected\"<\/code>) tuples in the preceding code. The test_square<\/code> test function will execute each of them one at a time, and the test report will be generated by determining whether the num<\/code> evaluated is equal to the expected value.<\/p>\n\n\n\nPytest Fixtures<\/h2>\n\n\n\n
pytest<\/code> fixtures, you can avoid duplicating setup code across multiple tests. By defining a function with the @pytest.fixture<\/code> decorator, you create a reusable setup that can be shared across multiple test functions or classes.<\/p>\n\n\n\n\n
collect_vehicle_number_from_delhi()<\/code> to extract vehicle numbers belonging to Delhi.<\/p>\n\n\n\n# fixtures_pytest.py\ndef collect_vehicle_number_from_delhi(vehicle_detail):\n data_collected = []\n for item in vehicle_detail:\n vehicle_number = item.get(\"vehicle_number\", \"\")\n if \"DL\" in vehicle_number:\n data_collected.append(f\"{vehicle_number}\")\n return data_collected<\/pre><\/div>\n\n\n\n# test_pytest_fixture.py\nfrom fixtures_pytest import collect_vehicle_number_from_delhi\n\ndef test_collect_vehicle_number_from_delhi():\n vehicle_detail = [\n {\n \"category\": \"Car\",\n \"vehicle_number\": \"DL04R1441\"\n },\n\n {\n \"category\": \"Bike\",\n \"vehicle_number\": \"HR04R1441\"\n },\n\n {\n \"category\": \"Car\",\n \"vehicle_number\": \"DL04R1541\"\n }\n ]\n\n expected_result = [\n \"DL04R1441\",\n \"DL04R1541\"\n ]\n\n assert collect_vehicle_number_from_delhi(vehicle_detail) == expected_result<\/pre><\/div>\n\n\n\ntest_collect_vehicle_number_from_delhi()<\/code> above determines whether or not the collect_vehicle_number_from_delhi()<\/code> function extracts the data as expected. Now you might want to extract the vehicle number belonging to another state, then you will write another function collect_vehicle_number_from_haryana()<\/code>.<\/p>\n\n\n\n# fixtures_pytest.py\ndef collect_vehicle_number_from_delhi(vehicle_detail):\n # Remaining code\n\ndef collect_vehicle_number_from_haryana(vehicle_detail):\n data_collected = []\n for item in vehicle_detail:\n vehicle_number = item.get(\"vehicle_number\", \"\")\n if \"HR\" in vehicle_number:\n data_collected.append(f\"{vehicle_number}\")\n return data_collected<\/pre><\/div>\n\n\n\n# test_pytest_fixture.py\nfrom fixtures_pytest import collect_vehicle_number_from_haryana\n\ndef test_collect_vehicle_number_from_haryana():\n vehicle_detail = [\n {\n \"category\": \"Car\",\n \"vehicle_number\": \"DL04R1441\"\n },\n\n {\n \"category\": \"Bike\",\n \"vehicle_number\": \"HR04R1441\"\n },\n\n {\n \"category\": \"Car\",\n \"vehicle_number\": \"DL04R1541\"\n }\n ]\n\n expected_result = [\n \"HR04R1441\"\n ]\n\n assert collect_vehicle_number_from_haryana(vehicle_detail) == expected_result<\/pre><\/div>\n\n\n\n@pytest.fixture<\/code> here.<\/p>\n\n\n\n# test_pytest_fixture.py\n\nimport pytest\nfrom fixtures_pytest import collect_vehicle_number_from_haryana\nfrom fixtures_pytest import collect_vehicle_number_from_delhi\n\n@pytest.fixture\ndef vehicle_data():\n return [\n {\n \"category\": \"Car\",\n \"vehicle_number\": \"DL04R1441\"\n },\n\n {\n \"category\": \"Bike\",\n \"vehicle_number\": \"HR04R1441\"\n },\n\n {\n \"category\": \"Car\",\n \"vehicle_number\": \"DL04R1541\"\n }\n ]\n\n# test 1\ndef test_collect_vehicle_number_from_delhi(vehicle_data):\n expected_result = [\n \"DL04R1441\",\n \"DL04R1541\"\n ]\n assert collect_vehicle_number_from_delhi(vehicle_data) == expected_result\n\n# test 2\ndef test_collect_vehicle_number_from_haryana(vehicle_data):\n expected_result = [\n \"HR04R1441\"\n ]\n assert collect_vehicle_number_from_haryana(vehicle_data) == expected_result<\/pre><\/div>\n\n\n\n@pytest.fixture<\/code> decorated function vehicle_data<\/code>.<\/p>\n\n\n\nFixture for Database Connection<\/h3>\n\n\n\n
# fixture_for_db_connection.py\n\nimport pytest\nimport sqlite3\n\n@pytest.fixture\ndef database_connection():\n # Setup Phase\n conn = sqlite3.connect(\":memory:\")\n cur = conn.cursor()\n\n cur.execute(\n \"CREATE TABLE users (name TEXT)\"\n )\n\n # Freeze the state and pass the object to test function\n yield conn\n\n # Teardown Phase\n conn.close()<\/pre><\/div>\n\n\n\n
database_connection()<\/code> is created, which creates an SQLite database in memory and establishes a connection, then creates a table, yields the connection, and finally closes the connection once the work is completed.<\/p>\n\n\n\n# fixture_for_db_connection.py\n\ndef test_insert_data(database_connection):\n database_connection.execute(\n \"INSERT INTO users (name) VALUES ('Virat Kohli')\"\n )\n\n res = database_connection.execute(\n \"SELECT * FROM users\"\n )\n result = res.fetchall()\n\n assert result is not None\n assert (\"Virat Kohli\",) in result<\/pre><\/div>\n\n\n\ntest_insert_data()<\/code> test function takes the database_connection<\/code> fixture as an argument, which eliminates the need to rewrite the database connection code.<\/p>\n\n\n\nMarkers in Pytest<\/h2>\n\n\n\n
@pytest.mark.parametrize<\/code> decorator. Well, @pytest.mark.parametrize<\/code> is a decorator that marks a test function for parametrization.<\/p>\n\n\n\nSkipping Tests<\/h3>\n\n\n\n
@pytest.mark.skip<\/code>.<\/p>\n\n\n\ntest_pytest_fixture.py<\/code> script, for example, you added two new test functions but want to skip testing them because you haven’t yet created the collect_vehicle_number_from_punjab()<\/code> and collect_vehicle_number_from_maharashtra()<\/code> functions to pass these tests.<\/p>\n\n\n\n# test_pytest_fixture.py\n\n# Previous code here\n\n@pytest.mark.skip(reason=\"Not implemented yet\")\ndef test_collect_vehicle_number_from_punjab(vehicle_data):\n expected_result = [\n \"PB3SQ4141\"\n ]\n assert collect_vehicle_number_from_punjab(vehicle_data) == expected_result\n\n\n@pytest.mark.skip(reason=\"Not implemented yet\")\ndef test_collect_vehicle_number_from_maharashtra(vehicle_data):\n expected_result = [\n \"MH05X1251\"\n ]\n assert collect_vehicle_number_from_maharashtra(vehicle_data) == expected_result<\/pre><\/div>\n\n\n\n
@pytest.mark.skip<\/code> and provide a reason for skipping. When you run this script, pytest will bypass these tests.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest test_pytest_fixture.py\n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 4 items\n\ntest_pytest_feature.py ..ss [100%]\n\n================================================================== 2 passed, 2 skipped in 0.05s ==================================================================<\/pre><\/div>\n\n\n\n
@pytest.mark.skipif<\/code> decorator to mark the test function. Here’s an illustration.<\/p>\n\n\n\n# test_pytest_fixture.py\n\n# Previous code here\n\n@pytest.mark.skipif(\n pytest.version_tuple < (7, 2), \n reason=\"pytest version is less than 7.2\"\n)\ndef test_collect_vehicle_number_from_punjab(vehicle_data):\n expected_result = [\n \"PB3SQ4141\"\n ]\n assert collect_vehicle_number_from_punjab(vehicle_data) == expected_result\n\n\n@pytest.mark.skipif(\n pytest.version_tuple < (7, 2), \n reason=\"pytest version is less than 7.2\"\n)\ndef test_collect_vehicle_number_from_karnataka(vehicle_data):\n expected_result = [\n \"KR3SQ4141\"\n ]\n assert collect_vehicle_number_from_karnataka(vehicle_data) == expected_result<\/pre><\/div>\n\n\n\n
test_collect_vehicle_number_from_punjab<\/code> and test_collect_vehicle_number_from_karnataka<\/code>) are decorated with @pytest.mark.skipif<\/code>. The condition specified in each case is pytest.version_tuple < (7, 2)<\/code>, which means that these tests will be skipped if the installed pytest<\/code> version is less than 7.2. The reason<\/code> parameter provides a message explaining why the tests are being skipped.<\/p>\n\n\n\nFilter Warnings<\/h3>\n\n\n\n
@pytest.mark.filterwarnings<\/code> function, allowing you to control which warnings are captured during tests.<\/p>\n\n\n\n# test_pytest_fixture.py\nimport warnings\n\n# Previous code here\n\n# Helper warning function\ndef warning_function():\n warnings.warn(\"Not implemented yet\", UserWarning)\n\n@pytest.mark.filterwarnings(\"error:Not implemented yet\")\ndef test_collect_vehicle_number_from_punjab(vehicle_data):\n warning_function()\n expected_result = [\"PB3SQ4141\"]\n assert collect_vehicle_number_from_punjab(vehicle_data) == expected_result\n\n\n@pytest.mark.filterwarnings(\"error:Not implemented yet\")\ndef test_collect_vehicle_number_from_karnataka(vehicle_data):\n warning_function()\n expected_result = [\"KR3SQ4141\"]\n assert collect_vehicle_number_from_karnataka(vehicle_data) == expected_result<\/pre><\/div>\n\n\n\n
warning_function()<\/code>).<\/p>\n\n\n\ntest_collect_vehicle_number_from_punjab<\/code> and test_collect_vehicle_number_from_karnataka<\/code>) are decorated with @pytest.mark.filterwarnings<\/code> which specifies that any UserWarning<\/code> with the message “Not implemented yet”<\/strong> should be treated as an error during the execution of these tests.<\/p>\n\n\n\nwarning_function<\/code> which, in turn, emits a UserWarning<\/code> with the specified message.<\/p>\n\n\n\npytest<\/code>, the warning is displayed.<\/p>\n\n\n\n==================================================================== short test summary info ===================================================================== \nFAILED test_pytest_feature.py::test_collect_vehicle_number_from_punjab - UserWarning: Not implemented yet\nFAILED test_pytest_feature.py::test_collect_vehicle_number_from_karnataka - UserWarning: Not implemented yet\n======================================================================= 2 failed in 0.31s ========================================================================<\/pre><\/div>\n\n\n\n
Pytest Command-line Options<\/h2>\n\n\n\n
pytest<\/code> options using the following command in your terminal.<\/p>\n\n\n\npytest --help<\/pre><\/div>\n\n\n\n
pytest<\/code> command-line options that you can try when you execute tests.<\/p>\n\n\n\nRunning Tests Using Keyword<\/h3>\n\n\n\n
-k<\/code> option with a keyword or expression. Assume you have the Python file test_sample.py<\/code>, which contains the tests listed below.<\/p>\n\n\n\ndef square(num):\n return num**2\n\n# Test 1\ndef test_special_one():\n a = 2\n assert square(a) == 4\n\n# Test 2\ndef test_special_two():\n x = 3\n assert square(x) == 9\n\n# Test 3\ndef test_normal_three():\n x = 3\n assert square(x) == 9<\/pre><\/div>\n\n\n\n
\"test_special\"<\/code>, use the following command.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest -k test_special \n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 3 items \/ 1 deselected \/ 2 selected\n\ntest_sample.py .. [100%]\n\n================================================================ 2 passed, 1 deselected in 0.07s =================================================================<\/pre><\/div>\n\n\n\n
\"test_special\"<\/code> in their name were selected, and the others were deselected.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest -k \"not test_special\"\n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 3 items \/ 2 deselected \/ 1 selected\n\ntest_sample.py . [100%] \n\n================================================================ 1 passed, 2 deselected in 0.06s =================================================================<\/pre><\/div>\n\n\n\n
\"not test_special\"<\/code> in the above command indicates that run only those tests that don’t have “test_special” in their name.<\/p>\n\n\n\nCustomizing Output<\/h3>\n\n\n\n
\n
-v<\/code>, --verbose<\/code> – Increases verbosity<\/li>\n\n\n\n--no-header<\/code> – Disables header<\/li>\n\n\n\n--no-summary<\/code> – Disables summary<\/li>\n\n\n\n-q<\/code>, --quiet<\/code> – Decreases verbosity<\/li>\n<\/ul>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest -v test_sample.py \n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0 -- D:\\SACHIN\\Python310\\python.exe\ncachedir: .pytest_cache\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 3 items \n\ntest_sample.py::test_special_one PASSED [ 33%] \ntest_sample.py::test_special_two PASSED [ 66%] \ntest_sample.py::test_normal_three PASSED [100%] \n\n======================================================================= 3 passed in 0.04s ========================================================================<\/pre><\/div>\n\n\n\n
D:\\SACHIN\\Pycharm\\pytestt_lib>pytest -q test_sample.py \n... [100%]\n3 passed in 0.02s<\/pre><\/div>\n\n\n\n
--no-header<\/code> and --no-summary<\/code> together, it is equivalent to using -q<\/code> (decreased verbosity).<\/p>\n\n\n\nTest Collection<\/h3>\n\n\n\n
--collect-only<\/code>, --co<\/code> option, pytest<\/code> collects all the tests but doesn’t execute them.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest --collect-only test_sample.py \n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 3 items\n\n<Module test_sample.py>\n <Function test_special_one>\n <Function test_special_two>\n <Function test_normal_three>\n\n=================================================================== 3 tests collected in 0.02s ===================================================================<\/pre><\/div>\n\n\n\n
Ignore Path or File during Test Collection<\/strong><\/h3>\n\n\n\n
--ignore=path<\/code> option.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest --ignore=test_sample.py\n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 1 item\n\ntest_square.py . [100%] \n\n======================================================================= 1 passed in 0.06s ========================================================================<\/pre><\/div>\n\n\n\n
test_sample.py<\/code> file is ignored by pytest<\/code> during test collection in the above example.<\/p>\n\n\n\nExit on First Failed Test or Error<\/h3>\n\n\n\n
-x<\/code>, --exitfirst<\/code> option, pytest<\/code> exits the test execution on the first failed test or error that it finds.<\/p>\n\n\n\nD:\\SACHIN\\Pycharm\\pytestt_lib>pytest -x test_sample.py\n====================================================================== test session starts =======================================================================\nplatform win32 -- Python 3.10.5, pytest-7.3.2, pluggy-1.0.0\nrootdir: D:\\SACHIN\\Pycharm\\pytestt_lib\nplugins: anyio-3.6.2\ncollected 3 items\n\ntest_sample.py F\n\n============================================================================ FAILURES ============================================================================ \n________________________________________________________________________ test_special_one ________________________________________________________________________ \n\n def test_special_one():\n a = 2\n> assert square(a) == 5\nE assert 4 == 5\nE + where 4 = square(2)\n\ntest_sample.py:6: AssertionError\n==================================================================== short test summary info ===================================================================== \nFAILED test_sample.py::test_special_one - assert 4 == 5\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! \n======================================================================= 1 failed in 0.35s ========================================================================<\/pre><\/div>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
\n
pytest<\/code> for testing your code<\/li>\n\n\n\npytest<\/code><\/li>\n\n\n\n
\n\n\n\n