Starting from pytest-asyncio's most recent release (version 0.19.0), strict mode is enforced by default 1, which requires the usage of @pytest.mark.asyncio and @pytest_asyncio.fixture2. Without these markers, tests and fixtures are not considered as asyncio-driven, resulting functional tests failures.
For charms using pytest framework, we need to update their functional tests by replacing the current used @pytest.fixture with @pytest_asyncio.fixture in test files.
Starting from
pytest-asyncio's most recent release (version 0.19.0), strict mode is enforced by default 1, which requires the usage of@pytest.mark.asyncioand@pytest_asyncio.fixture2. Without these markers, tests and fixtures are not considered as asyncio-driven, resulting functional tests failures.For charms using pytest framework, we need to update their functional tests by replacing the current used
@pytest.fixturewith@pytest_asyncio.fixturein test files.Imported from Launchpad using lp2gh.
date created: 2022-08-02T16:31:19Z
owner: txiao
assignee: txiao
the launchpad url