This executes the test runner by discovering all classes in this file that inherit from unittest.TestCase. This is one of many ways to execute the unittest test runner. When you have a single test file named test.py, calling python test.py is a great way to get started. Another way is using the unittest command line. Test Junkie is a modern full-featured Python testing framework with advanced test runner, reporting, and analytics engine. Retry, parametrize, skip, and prioritize tests and there is much more!
See also
In general, pytest is invoked with the command pytest (see below for other ways to invoke pytest). This will execute all tests in all files whose names follow the form test_*.py or *_test.pyin the current directory and its subdirectories. More generally, pytest follows standard test discovery rules.
Specifying which tests to run¶
Pytest supports several ways to run and select tests from the command-line.
Run tests in a module
Run tests in a directory
Run tests by keyword expressions
This will run tests which contain names that match the given string expression (case-insensitive),which can include Python operators that use filenames, class names and function names as variables.The example above will run TestMyClass.test_something but not TestMyClass.test_method_simple.
Run tests by node ids
Each collected test is assigned a unique nodeid which consist of the module filename followedby specifiers like class names, function names and parameters from parametrization, separated by :: characters.
To run a specific test within a module:
Another example specifying a test method in the command line:
Run tests by marker expressions
Python Html Test Runner
Will run all tests which are decorated with the @pytest.mark.slow decorator.
For more information see marks.
Run tests from packages
This will import pkg.testing and use its filesystem location to find and run tests from.
Getting help on version, option names, environment variables¶
Profiling test execution duration¶
To get a list of the slowest 10 test durations over 1.0s long:
By default, pytest will not show test durations that are too small (<0.005s) unless -vv is passed on the command-line.
Managing loading of plugins¶
Early loading plugins¶
You can early-load plugins (internal and external) explicitly in the command-line with the -p option:
The option receives a name parameter, which can be:
A full module dotted name, for example
myproject.plugins. This dotted name must be importable.The entry-point name of a plugin. This is the name passed to
setuptoolswhen the plugin isregistered. For example to early-load the pytest-cov plugin you can use:
Disabling plugins¶
To disable loading specific plugins at invocation time, use the -p optiontogether with the prefix no:.
Example: to disable loading the plugin doctest, which is responsible forexecuting doctest tests from text files, invoke pytest like this:
Other ways of calling pytest¶
Html Test Runner Python
Calling pytest through python-mpytest¶
You can invoke testing through the Python interpreter from the command line:
This is almost equivalent to invoking the command line script pytest[...]directly, except that calling via python will also add the current directory to sys.path.
Calling pytest from Python code¶
You can invoke pytest from Python code directly:
Python Test Runner Gui
this acts as if you would call “pytest” from the command line.It will not raise SystemExit but return the exit code instead.You can pass in options and arguments:
You can specify additional plugins to pytest.main:
Running it will show that MyPlugin was added and itshook was invoked:
Note
Playwright Test Runner Python
Calling pytest.main() will result in importing your tests and any modulesthat they import. Due to the caching mechanism of python’s import system,making subsequent calls to pytest.main() from the same process will notreflect changes to those files between the calls. For this reason, makingmultiple calls to pytest.main() from the same process (in order to re-runtests, for example) is not recommended.