pytest-asyncio
pytest-asyncio copied to clipboard
Asyncio support for pytest
this ugly hack causes the context to be preserved across all excursions into async land. this fixes https://github.com/pytest-dev/pytest-asyncio/issues/127
This is something I found useful and implemented in one of my own projects so I thought I'd make a PR in case the maintainers think this would be a...
I manage to use a global value `current_context`, that stores the current context after entering the async generator fixture. Apply it before running fixtures set up and test functions. Clean...
This is more an idea / question how hard it would be. While `pytest` ensures stable fixture order, it's made with synchronous fixtures in mind. `pytest-asyncio` on the other hand...
pytest-asyncio has dependencies on a bunch of other pytest plugins, in order to ensure mutual compatibility. These tests are run as part of the CI. CI will always install the...
If you have an async fixture with a teardown and `autouse=True` and you have a simple non-async test with a [pytester plugin](https://docs.pytest.org/en/7.0.x/how-to/writing_plugins.html#testing-plugins), then that fixture is always added as a...
It would be ideal to add an additional `clock_event_loop` fixture with a custom `AbstractEventLoop`. Instead, this one would only advance time explicitly similar to the `twisted.internet.task.Clock` useful for testing `twisted`...
Hi, I just ran into this - if you make a fixture method `async`, it is run with a different `self`, so you can't set attributes on `self` and read...
[aioloop-proxy](https://github.com/aio-libs/aioloop-proxy) provide a proxy instance that is fully compatible with `asyncio.AbstractEventLoop` but allows to cooperate of multiple nested proxies at the same time. From pytest-asyncio point of view, a session-scope...