for debugging purposes, a good combination is --lf --trace which would start a debug session with pdb at the beginning of the last test that failed:

pytest -l

If you start pytest with --pdb, it will start a pdb debugging session right after an exception is raised in your test. Most of the time this is not particularly useful as you might want to inspect each line of code before the raised exception.

pytest --lf

pytest -x

pytest --collect-only

pytest test_validator.py::test_regular_email_validates

Apart from shared fixtures you could place external hooks and plugins or modifiers for the PATH used by pytest to discover tests and implementation code.

pytest can read its project-specific configuration from one of these files: pytest.ini tox.ini setup.cfg

To have the fixture actually be used by one of your test, you simply add the fixture’s name as an argument

Fixtures are created when first requested by a test, and are destroyed based on their scope: function: the default scope, the fixture is destroyed at the end of the test.

When pytest goes to run a test, it looks at the parameters in that test function’s signature, and then searches for fixtures that have the same names as those parameters. Once pytest finds them, it runs those fixtures, captures what they returned (if anything), and passes those objects into the test function as arguments.

“Fixtures”, in the literal sense, are each of the arrange steps and data. They’re everything that test needs to do its thing.

The goal of this tutorial is to describe Python development ecosystem.

Comparison between pytest and unittes test frameworks

Support for running tests in parallel with pytest is available through the pytest-xdist package.

With pytest, failed tests also appear in the Problems panel, where you can double-click on an issue to navigate directly to the test

Testing in Python is disabled by default. To enable testing, use the Python: Configure Tests command on the Command Palette.

python.testing.pytestArgs: Looks for any Python (.py) file whose name begins with "test_" or ends with "_test", located anywhere within the current folder and all subfolders.

db.session.remove()

Good Integration Practices

Conventions for Python test discovery¶ pytest implements the following standard test discovery: If no arguments are specified then collection starts from testpaths (if configured) or the current directory. Alternatively, command line arguments can be used in any combination of directories, file names or node ids. recurse into directories, unless they match norecursedirs test_*.py or *_test.py files, imported by their test package name. Test prefixed test classes (without an __init__ method) test_ prefixed test functions or methods are test items For examples of how to customize your test discovery Changing standard (Python) test discovery. Within Python modules, pytest also discovers tests using the standard unittest.TestCase subclassing technique.

Conventions for Python test discovery¶ pytest implements the following standard test discovery: If no arguments are specified then collection starts from testpaths (if configured) or the current directory. Alternatively, command line arguments can be used in any combination of directories, file names or node ids. Recurse into directories, unless they match norecursedirs. In those directories, search for test_*.py or *_test.py files, imported by their test package name. From those files, collect test items: test_ prefixed test functions or methods outside of class test_ prefixed test functions or methods inside Test prefixed test classes (without an __init__ method) For examples of how to customize your test discovery Changing standard (Python) test discovery. Within Python modules, pytest also discovers tests using the standard unittest.TestCase subclassing technique.