This PR marks those tests as tests with expected failure if they're run under pytest 8+. If the situation doesn't change, we might remove explicit support of lazy-fixture entirely in the future.
Additional changes
Disable pytest plugin autoload
All poe testing tasks now run pytest with plugin autoload disabled (via the PYTEST_DISABLE_PLUGIN_AUTOLOAD env var). The outer session doesn't need any. And if an inner session requires some plugins, they are always enabled explicitly by the runner.
Context
Lazy-fixture is incompatible with pytest 8+ (see TvoroG/pytest-lazy-fixture#65 for more details). Because of this, our tests that check compatibility between allure-pytest and lazy-fixture fail (example: https://github.com/allure-framework/allure-python/actions/runs/7892006564/job/21537573652).
This PR marks those tests as tests with expected failure if they're run under pytest 8+. If the situation doesn't change, we might remove explicit support of
lazy-fixtureentirely in the future.Additional changes
Disable pytest plugin autoload
All poe testing tasks now run pytest with plugin autoload disabled (via the
PYTEST_DISABLE_PLUGIN_AUTOLOADenv var). The outer session doesn't need any. And if an inner session requires some plugins, they are always enabled explicitly by the runner.