معرفی شرکت ها
alt-pytest-asyncio-0.6.0
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشترتوضیحات
Alternative pytest plugin to pytest-asyncio
| ویژگی | مقدار |
|---|---|
| سیستم عامل | - |
| نام فایل | alt-pytest-asyncio-0.6.0 |
| نام | alt-pytest-asyncio |
| نسخه کتابخانه | 0.6.0 |
| نگهدارنده | [] |
| ایمیل نگهدارنده | [] |
| نویسنده | Stephen Moore |
| ایمیل نویسنده | delfick755@gmail.com |
| آدرس صفحه اصلی | https://github.com/delfick/alt-pytest-asyncio |
| آدرس اینترنتی | https://pypi.org/project/alt-pytest-asyncio/ |
| مجوز | MIT |
Alternative Pytest Asyncio
==========================
This plugin allows you to have async pytest fixtures and tests.
This plugin only supports python 3.6 and above.
The code here is influenced by pytest-asyncio but with some differences:
* Error tracebacks from are from your tests, rather than asyncio internals
* There is only one loop for all of the tests
* You can manage the lifecycle of the loop yourself outside of pytest by using
this plugin with your own loop
* No need to explicitly mark your tests as async. (pytest-asyncio requires you
mark your async tests because it also supports other event loops like curio
and trio)
Like pytest-asyncio it supports async tests, coroutine fixtures and async
generator fixtures.
Changelog
---------
0.6.0 - 23 October 2021
* Fix bug where it was possible for an async generator fixture to
be cleaned up even if it was never started.
* This library is now 3.7+ only
* Added an equivalent ``shutdown_asyncgen`` to the OverrideLoop helper
0.5.4 - 26 January 2021
* Added a ``--default-async-timeout`` option from the CLI. With many thanks
to @andredias.
* Renamed existing pytest.ini option from ``default_alt_async_timeout`` to
be ``default_async_timeout``.
0.5.3 - 25 July 2020
* Make sure a KeyboardInterrupt on running tests still shows errors from
failed tests
0.5.2 - 6 February 2020
* Added ability to make a different event loop for some tests
0.5.1 - 15 December 2019
* Added an ini option ``default_alt_async_timeout`` for the default async
timeout for fixtures and tests. The default is now 5 seconds. So say
you wanted the default to be 3.5 seconds, you would set
``default_alt_async_timeout`` to be 3.5
0.5 - 16 August 2019
* I made this functionality in a work project where I needed to run
pytest.main from an existing event loop. I decided to make this it's
own module so I can have tests for this code.
Running from your own event loop
--------------------------------
If you want to run pytest.main from with an existing event loop then you can
do something like:
.. code-block:: python
from alt_pytest_asyncio.plugin import AltPytestAsyncioPlugin, run_coro_as_main
import nest_asyncio
import asyncio
import pytest
async def my_tests():
await do_some_setup_before_pytest()
plugins = [AltPytestAsyncioPlugin(loop)]
try:
code = pytest.main([], plugins=plugins)
finally:
# Note that alt_pytest_asyncio will make sure all your async tests
# have been finalized by this point, even if you KeyboardInterrupt
# the pytest.main
await do_any_teardown_after_pytest()
if code != 0:
raise Exception(repr(code))
if __name__ == '__main__':
# Nest asyncio is required so that we can do run_until_complete in an
# existing event loop - https://github.com/erdewit/nest_asyncio
loop = asyncio.get_event_loop()
nest_asyncio.apply(loop)
run_coro_as_main(loop, my_tests())
Note that if you don't need to run pytest from an existing event loop, you don't
need to do anything other than have alt_pytest_asyncio installed in your
environment and you'll be able to just use async keywords on your fixtures and
tests.
Timeouts
--------
alt_pytest_asyncio registers a ``pytest.mark.async_timeout(seconds)`` mark which
you can use to set a timeout for your test.
For example:
.. code-block:: python
import pytest
@pytest.mark.async_timeout(10)
async def test_something():
await something_that_may_take_a_while()
This test will be cancelled after 10 seconds and raise an assertion error saying
the test took too long and the file and line number where the test is.
You can also use the async_timeout mark on coroutine fixtures:
.. code-block:: python
import pytest
@pytest.fixture()
@pytest.mark.async_timeout(0.5)
async def my_amazing_fixture():
await asyncio.sleep(1)
return 1
And you can have a timeout on generator fixtures:
.. code-block:: python
import pytest
@pytest.fixture()
@pytest.mark.async_timeout(0.5)
async def my_amazing_fixture():
try:
await asyncio.sleep(1)
yield 1
finally:
await asyncio.sleep(1)
Note that for generator fixtures, the timeout is applied in whole to both the
setup and finalization of the fixture. As in the real timeout for the entire
fixture is essentially double the single timeout specified.
The default timeout is 5 seconds. You can change this default by setting the
``default_async_timeout`` option to the number of seconds you want.
This setting is also available from the CLI using the ``--default-async-timeout``
option.
Overriding the loop
-------------------
Sometimes it may be necessary to close the current loop in a test. For this to
not then break the rest of your tests, you will need to set a new event loop for
your test and then restore the old loop afterwards.
For this, we have a context manager that will install a new asyncio loop and
then restore the original loop on exit.
Usage looks like::
from alt_pytest_asyncio.plugin import OverrideLoop
class TestThing:
@pytest.fixture(autouse=True)
def custom_loop(self):
with OverrideLoop() as custom_loop:
yield custom_loop
def test_thing(self, custom_loop):
custom_loop.run_until_complete(my_thing())
By putting the loop into an autouse fixture, all fixtures used by the test
will have the custom loop. If you want to include module level fixtures too
then use the OverrideLoop in a module level fixture too.
OverrideLoop takes in a ``new_loop`` boolean that will make it so no new
loop is set and asyncio is left with no default loop.
The new loop itself (or None if new_loop is False) can be found in the
``loop`` attribute of the object yielded by the context manager.
The ``run_until_complete`` on the ``custom_loop`` in the above example will
do a ``run_until_complete`` on the new loop, but in a way that means you
won't get ``unhandled exception during shutdown`` errors when the context
manager closes the new loop.
When the context manager exits and closes the new loop, it will first cancel
all tasks to ensure finally blocks are run.
زبان مورد نیاز
| مقدار | نام |
|---|---|
| >= 3.7 | Python |
نحوه نصب
نصب پکیج whl alt-pytest-asyncio-0.6.0:
pip install alt-pytest-asyncio-0.6.0.whl
نصب پکیج tar.gz alt-pytest-asyncio-0.6.0:
pip install alt-pytest-asyncio-0.6.0.tar.gz