[checkmk-commits] [tribe29/checkmk] 3b77c2: Check plugin loading fixtures not loading automati...

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 3b77c25984b1c87ff7f7f068bb8dce41b467800d https://github.com/tribe29/checkmk/commit/3b77c25984b1c87ff7f7f068bb8dce41b… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2020-09-14 (Mon, 14 Sep 2020) Changed paths: M tests/testlib/__init__.py M tests/unit/checks/generictests/datasets/docker_node_disk_usage_raw_text.py M tests/unit/checks/generictests/datasets/docker_node_disk_usage_regression.py M tests/unit/checks/generictests/datasets/docker_node_info_centos6_regression.py M tests/unit/checks/generictests/datasets/docker_node_info_no_output.py M tests/unit/checks/generictests/datasets/docker_node_info_raw_text.py M tests/unit/checks/test_generic_legacy_conversion.py M tests/unit/cmk/base/data_sources/test_cmd_caching.py M tests/unit/conftest.py Log Message: ----------- Check plugin loading fixtures not loading automatically anymore These fixtures must not be used automatically! They significantly slow down the initialization of all our unit tests, especially when only executing a small subset of the tests. We have to be more specific. This functionality was moved to the top-level conftest.py in 195238faf7d with the intention to prevent plugins from being loaded multiple times. The scope of this fixture is preventing that. This is fine. But the autouse is not OK. Since we have now removed "automatic loading of all checks", there were some additional cleanups needed to make the tests work again. Change-Id: Icd03cc0160d36e9204d88e378f0804a44ba290fe