allure-python incompatibility with pytest-asyncio-cooperative

[rhyspang]

@allure.feature('page')
class TestPage(object):
    @allure.story('story1')
    @pytest.mark.asyncio_cooperative
    async def test_01(self):
        with allure.step("execute test_02"):
            # await asyncio.sleep(1)
            print("test_01")

allure-python incompatibility with pytest-asyncio-cooperative. Test cases are displayed in the report. but no execution details are shown
No information about test execution is available.

[delatrie]

This is because pytest-asyncio-cooperative messes with an expected lifecycle of a test. It calls a test function directly inside its own event loop before allure-pytest even knows that there actually is a test function. So, when the test steps are created allure-pytest cannot relate them to a test result and basically throws them away.

Here is the place, where test function is called by pytest-asyncio-cooperative (through test_wrapper):

pytest-asyncio-cooperative/pytest_asyncio_cooperative/plugin.py

Line 239 in 776424c

tasks[i] = asyncio.create_task(tasks[i])

And only when the test is done pytest_runtest_protocol hook is called here:

pytest-asyncio-cooperative/pytest_asyncio_cooperative/plugin.py

Line 289 in 776424c

item.ihook.pytest_runtest_protocol(item=item, nextitem=None)

And then, deep inside pytest, pytest_runtest_call creates the test result and pytest_runtest_logfinish closes it. Since the steps were already thrown away at this point the test result remains empty.

If we put pytest-asyncio-cooperative away, the test function will be executed between those two hooks making the steps available for allure-pytest. It basically happens here:
https://github.com/pytest-dev/pytest/blob/3af3f569d5394bb1a18426b0d57a04a094800974/src/_pytest/runner.py#L109