How would you use ward with asyncio/trio/curio?

from ward import test, xfail


@xfail('but seriously.')
@test('async functions should fail')
async def _():
    assert False

Naturally this should not pass, but indeed it does.

So I tried writing a decorator just to see if I could force the async to be sync.

import functools as ft
import asyncio

from ward import test, xfail


def async_test(fn):
    @ft.wraps(fn)
    def _async_wrapper(*args, **kwargs):
        loop = asyncio.get_event_loop()
        return loop.run_until_complete(fn(*args, **kwargs))

    return _async_wrapper


@xfail('but seriously.')
@test('async functions should fail')
@async_test
async def _():
    assert False

and it passed! … but I know for certain it’s not actually working. I can put literally anything in the anon function under @async_test and ward will tell me it passes.

So my assumption is that ward currently will not support async testing… but maybe I’m not smart enough to figure it out. :~)

- SN

[darrenburns]

Just as an update to this, after thinking about it I’ve got an update planned that’ll allow you to define your tests with async def and just use the standard @test decorator:

It still needs work, but hopefully this will land soon!

[boonhapus]

Interesting. I’m admittedly new to the world of async testing, so I’m not aware of what is/isn’t standard practice. It makes sense to me why there is a need for a synchronous runner, even if tests are async in isolation.