-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins loaded via PYTEST_PLUGINS
or pytest_plugins
are not reported
#12615
Comments
I found that with the following patch: --- /usr/lib/python3.9/vendor-packages/_pytest/config/__init__.py.orig
+++ /usr/lib/python3.9/vendor-packages/_pytest/config/__init__.py
@@ -835,7 +835,7 @@
) -> None:
plugins = _get_plugin_specs_as_list(spec)
for import_spec in plugins:
- self.import_plugin(import_spec)
+ self.import_plugin(import_spec, consider_entry_points=True)
def import_plugin(self, modname: str, consider_entry_points: bool = False) -> None:
"""Import a plugin with ``modname``. the $ env - PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 PYTEST_PLUGINS=randomly pytest --setup-plan
============================= test session starts ==============================
platform sunos5 -- Python 3.9.19, pytest-8.2.2, pluggy-1.5.0
Using --randomly-seed=1218696459
rootdir: /tmp/test
plugins: randomly-3.15.0
collected 0 items
============================ no tests ran in 0.03s =============================
$ |
This fixes two issues related to the `PYTEST_PLUGINS` environment variable and `pytest_plugins` global variable: * plugins loaded this way are not listed in the list of plugins, * it is not possible to load plugins using their names in `entry_points.txt` files. Fixes pytest-dev#12615.
This fixes two issues related to the `PYTEST_PLUGINS` environment variable and `pytest_plugins` global variable: * plugins loaded this way are not listed in the list of plugins, * it is not possible to load plugins using their names in `entry_points.txt` files. Fixes pytest-dev#12615.
This fixes two issues related to the `PYTEST_PLUGINS` environment variable and `pytest_plugins` global variable: * plugins loaded this way are not listed in the list of plugins, * it is not possible to load plugins using their names in `entry_points.txt` files. Fixes pytest-dev#12615.
This fixes two issues related to the `PYTEST_PLUGINS` environment variable and `pytest_plugins` global variable: * plugins loaded this way are not listed in the list of plugins, * it is not possible to load plugins using their names in `entry_points.txt` files. Fixes pytest-dev#12615.
This fixes two issues related to the `PYTEST_PLUGINS` environment variable and `pytest_plugins` global variable: * plugins loaded this way are not listed in the list of plugins, * it is not possible to load plugins using their names in `entry_points.txt` files. See pytest-dev#12615.
This was split out to #12624. |
The problem seems to be in the import_plugin() function. |
PYTEST_PLUGINS
environment variable are not reportedPYTEST_PLUGINS
or pytest_plugins
are not reported
pip list
from the virtual environment you are usingWhen I load a plugin using the
PYTEST_ADDOPTS
environment variable then the plugin is properly reported in the list of plugins:When I try to achieve the same using the
PYTEST_PLUGINS
environment variable then the plugin is not listed in the list of plugins:but the plugin is apparently properly loaded (please note
--randomly-seed
).It would be great to see plugins loaded via the
PYTEST_PLUGINS
environment variable reported too to avoid confusion.EDIT: the same problem is seen when the
pytest_plugins
global variable is used to load plugins.The text was updated successfully, but these errors were encountered: