Repository: allenporter/rtsp-to-webrtc-client (language: python)

Issue:
Update group:pytest
[![WhiteSource Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [pytest](https://docs.pytest.org/en/latest/) ([source](https://togithub.com/pytest-dev/pytest), [changelog](https://docs.pytest.org/en/stable/changelog.html)) | `==7.0.0` -> `==7.0.1` | [![age](https://badges.renovateapi.com/packages/pypi/pytest/7.0.1/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/pypi/pytest/7.0.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/pypi/pytest/7.0.1/compatibility-slim/7.0.0)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/pypi/pytest/7.0.1/confidence-slim/7.0.0)](https://docs.renovatebot.com/merge-confidence/) |
| [pytest-aiohttp](https://togithub.com/aio-libs/pytest-aiohttp) ([changelog](https://togithub.com/aio-libs/pytest-aiohttp/blob/master/CHANGES.rst)) | `==1.0.3` -> `==1.0.4` | [![age](https://badges.renovateapi.com/packages/pypi/pytest-aiohttp/1.0.4/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/pypi/pytest-aiohttp/1.0.4/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/pypi/pytest-aiohttp/1.0.4/compatibility-slim/1.0.3)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/pypi/pytest-aiohttp/1.0.4/confidence-slim/1.0.3)](https://docs.renovatebot.com/merge-confidence/) |
| [pytest-asyncio](https://togithub.com/pytest-dev/pytest-asyncio) | `==0.17.2` -> `==0.18.1` | [![age](https://badges.renovateapi.com/packages/pypi/pytest-asyncio/0.18.1/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/pypi/pytest-asyncio/0.18.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/pypi/pytest-asyncio/0.18.1/compatibility-slim/0.17.2)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/pypi/pytest-asyncio/0.18.1/confidence-slim/0.17.2)](https://docs.renovatebot.com/merge-confidence/) |

---

### Release Notes

<details>
<summary>pytest-dev/pytest</summary>

### [`v7.0.1`](https://togithub.com/pytest-dev/pytest/releases/7.0.1)

[Compare Source](https://togithub.com/pytest-dev/pytest/compare/7.0.0...7.0.1)

# pytest 7.0.1 (2022-02-11)

## Bug Fixes

-   [#&#8203;9608](https://togithub.com/pytest-dev/pytest/issues/9608): Fix invalid importing of `importlib.readers` in Python 3.9.
-   [#&#8203;9610](https://togithub.com/pytest-dev/pytest/issues/9610): Restore \[UnitTestFunction.obj]{.title-ref} to return unbound rather than bound method.
    Fixes a crash during a failed teardown in unittest TestCases with non-default \[\__init\_\_]{.title-ref}.
    Regressed in pytest 7.0.0.
-   [#&#8203;9636](https://togithub.com/pytest-dev/pytest/issues/9636): The `pythonpath` plugin was renamed to `python_path`. This avoids a conflict with the `pytest-pythonpath` plugin.
-   [#&#8203;9642](https://togithub.com/pytest-dev/pytest/issues/9642): Fix running tests by id with `::` in the parametrize portion.
-   [#&#8203;9643](https://togithub.com/pytest-dev/pytest/issues/9643): Delay issuing a `~pytest.PytestWarning`{.interpreted-text role="class"} about diamond inheritance involving `~pytest.Item`{.interpreted-text role="class"} and
    `~pytest.Collector`{.interpreted-text role="class"} so it can be filtered using `standard warning filters <warnings>`{.interpreted-text role="ref"}.

</details>

<details>
<summary>aio-libs/pytest-aiohttp</summary>

### [`v1.0.4`](https://togithub.com/aio-libs/pytest-aiohttp/blob/HEAD/CHANGES.rst#&#8203;104-2022-02-12)

[Compare Source](https://togithub.com/aio-libs/pytest-aiohttp/compare/v1.0.3...v1.0.4)

-   Fix failure with `aiohttp_client` fixture usage when `asyncio_mode=strict`.
    `#&#8203;25 <https://github.com/aio-libs/pytest-aiohttp/issue/25>`\_

</details>

<details>
<summary>pytest-dev/pytest-asyncio</summary>

### [`v0.18.1`](https://togithub.com/pytest-dev/pytest-asyncio/releases/v0.18.1)

[Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.18.0...v0.18.1)

***

## title: 'pytest-asyncio: pytest support for asyncio'

[![image](https://img.shields.io/pypi/v/pytest-asyncio.svg)](https://pypi.python.org/pypi/pytest-asyncio)

[![image](https://togithub.com/pytest-dev/pytest-asyncio/workflows/CI/badge.svg)](https://togithub.com/pytest-dev/pytest-asyncio/actions?workflow=CI)

[![image](https://codecov.io/gh/pytest-dev/pytest-asyncio/branch/master/graph/badge.svg)](https://codecov.io/gh/pytest-dev/pytest-asyncio)

[![Supported Python versions](https://img.shields.io/pypi/pyversions/pytest-asyncio.svg)](https://togithub.com/pytest-dev/pytest-asyncio)

[![image](https://img.shields.io/badge/code%20style-black-000000.svg)](https://togithub.com/ambv/black)

pytest-asyncio is an Apache2 licensed library, written in Python, for
testing asyncio code with pytest.

asyncio code is usually written in the form of coroutines, which makes
it slightly more difficult to test using normal testing tools.
pytest-asyncio provides useful fixtures and markers to make testing
easier.

```{.sourceCode .python}
@&#8203;pytest.mark.asyncio
async def test_some_asyncio_code():
    res = await library.do_something()
    assert b"expected result" == res
```

pytest-asyncio has been strongly influenced by
[pytest-tornado](https://togithub.com/eugeniy/pytest-tornado).

# Features

-   fixtures for creating and injecting versions of the asyncio event
    loop
-   fixtures for injecting unused tcp/udp ports
-   pytest markers for treating tests as asyncio coroutines
-   easy testing with non-default event loops
-   support for \[async def]{.title-ref} fixtures and async generator
    fixtures
-   support *auto* mode to handle all async fixtures and tests
    automatically by asyncio; provide *strict* mode if a test suite
    should work with different async frameworks simultaneously, e.g.
    `asyncio` and `trio`.

# Installation

To install pytest-asyncio, simply:

```{.sourceCode .bash}
$ pip install pytest-asyncio
```

This is enough for pytest to pick up pytest-asyncio.

# Modes

Starting from `pytest-asyncio>=0.17`, three modes are provided: *auto*,
*strict* and *legacy* (default).

The mode can be set by `asyncio_mode` configuration option in
[configuration
file](https://docs.pytest.org/en/latest/reference/customize.html):

```{.sourceCode .ini}
### pytest.ini
[pytest]
asyncio_mode = auto
```

The value can be overridden by command-line option for `pytest`
invocation:

```{.sourceCode .bash}
$ pytest tests --asyncio-mode=strict
```

## Auto mode

When the mode is auto, all discovered *async* tests are considered
*asyncio-driven* even if they have no `@pytest.mark.asyncio` marker.

All async fixtures are considered *asyncio-driven* as well, even if they
are decorated with a regular `@pytest.fixture` decorator instead of
dedicated `@pytest_asyncio.fixture` counterpart.

*asyncio-driven* means that tests and fixtures are executed by
`pytest-asyncio` plugin.

This mode requires the simplest tests and fixtures configuration and is
recommended for default usage *unless* the same project and its test
suite should execute tests from different async frameworks, e.g.
`asyncio` and `trio`. In this case, auto-handling can break tests
designed for other framework; please use *strict* mode instead.

## Strict mode

Strict mode enforces `@pytest.mark.asyncio` and
`@pytest_asyncio.fixture` usage. Without these markers, tests and
fixtures are not considered as *asyncio-driven*, other pytest plugin can
handle them.

Please use this mode if multiple async frameworks should be combined in
the same test suite.

## Legacy mode

This mode follows rules used by `pytest-asyncio<0.17`: tests are not
auto-marked but fixtures are.

This mode is used by default for the sake of backward compatibility,
deprecation warnings are emitted with suggestion to either switching to
`auto` mode or using `strict` mode with `@pytest_asyncio.fixture`
decorators.

In future, the default will be changed.

# Fixtures

## `event_loop`

Creates and injects a new instance of the default asyncio event loop. By
default, the loop will be closed at the end of the test (i.e. the
default fixture scope is `function`).

Note that just using the `event_loop` fixture won't make your test
function a coroutine. You'll need to interact with the event loop
directly, using methods like `event_loop.run_until_complete`. See the
`pytest.mark.asyncio` marker for treating test functions like
coroutines.

Simply using this fixture will not set the generated event loop as the
default asyncio event loop, or change the asyncio event loop policy in
any way. Use `pytest.mark.asyncio` for this purpose.

```{.sourceCode .python}
def test_http_client(event_loop):
    url = "http://httpbin.org/get"
    resp = event_loop.run_until_complete(http_client(url))
    assert b"HTTP/1.1 200 OK" in resp
```

This fixture can be easily overridden in any of the standard pytest
locations (e.g. directly in the test file, or in `conftest.py`) to use a
non-default event loop. This will take effect even if you're using the
`pytest.mark.asyncio` marker and not the `event_loop` fixture directly.

```{.sourceCode .python}
@&#8203;pytest.fixture
def event_loop():
    loop = MyCustomLoop()
    yield loop
    loop.close()
```

If the `pytest.mark.asyncio` marker is applied, a pytest hook will
ensure the produced loop is set as the default global loop. Fixtures
depending on the `event_loop` fixture can expect the policy to be
properly modified when they run.

## `unused_tcp_port`

Finds and yields a single unused TCP port on the localhost interface.
Useful for binding temporary test servers.

## `unused_tcp_port_factory`

A callable which returns a different unused TCP port each invocation.
Useful when several unused TCP ports are required in a test.

```{.sourceCode .python}
def a_test(unused_tcp_port_factory):
    port1, port2 = unused_tcp_port_factory(), unused_tcp_port_factory()
    ...
```

## `unused_udp_port` and `unused_udp_port_factory`

Work just like their TCP counterparts but return unused UDP ports.

## Async fixtures

Asynchronous fixtures are defined just like ordinary pytest fixtures,
except they should be decorated with `@pytest_asyncio.fixture`.

```{.sourceCode .python3}
import pytest_asyncio

@&#8203;pytest_asyncio.fixture
async def async_gen_fixture():
    await asyncio.sleep(0.1)
    yield "a value"

@&#8203;pytest_asyncio.fixture(scope="module")
async def async_fixture():
    return await asyncio.sleep(0.1)
```

All scopes are supported, but if you use a non-function scope you will
need to redefine the `event_loop` fixture to have the same or broader
scope. Async fixtures need the event loop, and so must have the same or
narrower scope than the `event_loop` fixture.

*auto* and *legacy* mode automatically converts async fixtures declared
with the standard `@pytest.fixture` decorator to *asyncio-driven*
versions.

# Markers

## `pytest.mark.asyncio`

Mark your test coroutine with this marker and pytest will execute it as
an asyncio task using the event loop provided by the `event_loop`
fixture. See the introductory section for an example.

The event loop used can be overridden by overriding the `event_loop`
fixture (see above).

In order to make your test code a little more concise, the pytest
`pytestmark`\_ feature can be used to mark entire modules or classes
with this marker. Only test coroutines will be affected (by default,
coroutines prefixed by `test_`), so, for example, fixtures are safe to
define.

```{.sourceCode .python}
import asyncio

import pytest
### All test coroutines will be treated as marked.
pytestmark = pytest.mark.asyncio

async def test_example(event_loop):
    """No marker!"""
    await asyncio.sleep(0, loop=event_loop)
```

In *auto* mode, the `pytest.mark.asyncio` marker can be omitted, the
marker is added automatically to *async* test functions.

# Note about unittest

Test classes subclassing the standard
[unittest](https://docs.python.org/3/library/unittest.html) library are
not supported, users are recommended to use
[unitest.IsolatedAsyncioTestCase](https://docs.python.org/3/library/unittest.html#unittest.IsolatedAsyncioTestCase)
or an async framework such as
[asynctest](https://asynctest.readthedocs.io/en/latest).

# Changelog

## 0.18.1 (22-02-10)

-   Fixes a regression that prevented async fixtures from working in
    synchronous tests.
    [#&#8203;286](https://togithub.com/pytest-dev/pytest-asyncio/issues/286)

## 0.18.0 (22-02-07)

-   Raise a warning if [@&#8203;pytest](https://togithub.com/pytest).mark.asyncio is applied to non-async
    function.
    [#&#8203;275](https://togithub.com/pytest-dev/pytest-asyncio/issues/275)
-   Support parametrized `event_loop` fixture.
    [#&#8203;278](https://togithub.com/pytest-dev/pytest-asyncio/issues/278)

## 0.17.2 (22-01-17)

-   Require `typing-extensions` on Python<3.8 only.
    [#&#8203;269](https://togithub.com/pytest-dev/pytest-asyncio/issues/269)
-   Fix a regression in tests collection introduced by 0.17.1, the
    plugin works fine with non-python tests again.
    [#&#8203;267](https://togithub.com/pytest-dev/pytest-asyncio/issues/267)

## 0.17.1 (22-01-16)

-   Fixes a bug that prevents async Hypothesis tests from working
    without explicit `asyncio` marker when `--asyncio-mode=auto` is set.
    [#&#8203;258](https://togithub.com/pytest-dev/pytest-asyncio/issues/258)
-   Fixed a bug that closes the default event loop if the loop doesn't
    exist
    [#&#8203;257](https://togithub.com/pytest-dev/pytest-asyncio/issues/257)
-   Added type annotations.
    [#&#8203;198](https://togithub.com/pytest-dev/pytest-asyncio/issues/198)
-   Show asyncio mode in pytest report headers.
    [#&#8203;266](https://togithub.com/pytest-dev/pytest-asyncio/issues/266)
-   Relax `asyncio_mode` type definition; it allows to support pytest
    6.1+.
    [#&#8203;262](https://togithub.com/pytest-dev/pytest-asyncio/issues/262)

## 0.17.0 (22-01-13)

-   \[pytest-asyncio]{.title-ref} no longer alters existing event loop
    policies.
    [#&#8203;168](https://togithub.com/pytest-dev/pytest-asyncio/issues/168),
    [#&#8203;188](https://togithub.com/pytest-dev/pytest-asyncio/issues/168)
-   Drop support for Python 3.6
-   Fixed an issue when pytest-asyncio was used in combination with
    \[flaky]{.title-ref} or inherited asynchronous Hypothesis tests.
    [#&#8203;178](https://togithub.com/pytest-dev/pytest-asyncio/issues/178)
    [#&#8203;231](https://togithub.com/pytest-dev/pytest-asyncio/issues/231)
-   Added [flaky](https://pypi.org/project/flaky/) to test dependencies
-   Added `unused_udp_port` and `unused_udp_port_factory` fixtures
    (similar to `unused_tcp_port` and `unused_tcp_port_factory`
    counterparts.
    [#&#8203;99](https://togithub.com/pytest-dev/pytest-asyncio/issues/99)
-   Added the plugin modes: *strict*, *auto*, and *legacy*. See
    [documentation](https://togithub.com/pytest-dev/pytest-asyncio#modes)
    for details.
    [#&#8203;125](https://togithub.com/pytest-dev/pytest-asyncio/issues/125)
-   Correctly process `KeyboardInterrupt` during async fixture setup
    phase
    [#&#8203;219](https://togithub.com/pytest-dev/pytest-asyncio/issues/219)

## 0.16.0 (2021-10-16)

-   Add support for Python 3.10

## 0.15.1 (2021-04-22)

-   Hotfix for errors while closing event loops while replacing them.
    [#&#8203;209](https://togithub.com/pytest-dev/pytest-asyncio/issues/209)
    [#&#8203;210](https://togithub.com/pytest-dev/pytest-asyncio/issues/210)

## 0.15.0 (2021-04-19)

-   Add support for Python 3.9
-   Abandon support for Python 3.5. If you still require support for
    Python 3.5, please use pytest-asyncio v0.14 or earlier.
-   Set `unused_tcp_port_factory` fixture scope to 'session'.
    [#&#8203;163](https://togithub.com/pytest-dev/pytest-asyncio/pull/163)
-   Properly close event loops when replacing them.
    [#&#8203;208](https://togithub.com/pytest-dev/pytest-asyncio/issues/208)

## 0.14.0 (2020-06-24)

-   Fix
    [#&#8203;162](https://togithub.com/pytest-dev/pytest-asyncio/issues/162),
    and `event_loop` fixture behavior now is coherent on all scopes.
    [#&#8203;164](https://togithub.com/pytest-dev/pytest-asyncio/pull/164)

## 0.12.0 (2020-05-04)

-   Run the event loop fixture as soon as possible. This helps with
    fixtures that have an implicit dependency on the event loop.
    [#&#8203;156](https://togithub.com/pytest-dev/pytest-asyncio/pull/156)

## 0.11.0 (2020-04-20)

-   Test on 3.8, drop 3.3 and 3.4. Stick to 0.10 for these versions.
    [#&#8203;152](https://togithub.com/pytest-dev/pytest-asyncio/pull/152)
-   Use the new Pytest 5.4.0 Function API. We therefore depend on
    pytest >= 5.4.0.
    [#&#8203;142](https://togithub.com/pytest-dev/pytest-asyncio/pull/142)
-   Better `pytest.skip` support.
    [#&#8203;126](https://togithub.com/pytest-dev/pytest-asyncio/pull/126)

## 0.10.0 (2019-01-08)

-   `pytest-asyncio` integrates with
    [Hypothesis](https://hypothesis.readthedocs.io) to support `@given`
    on async test functions using `asyncio`.
    [#&#8203;102](https://togithub.com/pytest-dev/pytest-asyncio/pull/102)
-   Pytest 4.1 support.
    [#&#8203;105](https://togithub.com/pytest-dev/pytest-asyncio/pull/105)

## 0.9.0 (2018-07-28)

-   Python 3.7 support.
-   Remove `event_loop_process_pool` fixture and
    `pytest.mark.asyncio_process_pool` marker (see
    <https://bugs.python.org/issue34075> for deprecation and removal
    details)

## 0.8.0 (2017-09-23)

-   Improve integration with other packages (like aiohttp) with more
    careful event loop handling.
    [#&#8203;64](https://togithub.com/pytest-dev/pytest-asyncio/pull/64)

## 0.7.0 (2017-09-08)

-   Python versions pre-3.6 can use the async_generator library for
    async fixtures. \[[#&#8203;62](https://togithub.com/pytest-dev/pytest-asyncio/issues/62)
 [https://github.com/pytest-dev/pytest-asyncio/pull/62](https://togithub.com/pytest-dev/pytest-asyncio/pull/62)ll/62>]{.title-ref}

## 0.6.0 (2017-05-28)

-   Support for Python versions pre-3.5 has been dropped.
-   `pytestmark` now works on both module and class level.
-   The `forbid_global_loop` parameter has been removed.
-   Support for async and async gen fixtures has been added.
    [#&#8203;45](https://togithub.com/pytest-dev/pytest-asyncio/pull/45)
-   The deprecation warning regarding `asyncio.async()` has been fixed.
    [#&#8203;51](https://togithub.com/pytest-dev/pytest-asyncio/pull/51)

## 0.5.0 (2016-09-07)

-   Introduced a changelog.
    [#&#8203;31](https://togithub.com/pytest-dev/pytest-asyncio/issues/31)
-   The `event_loop` fixture is again responsible for closing itself.
    This makes the fixture slightly harder to correctly override, but
    enables other fixtures to depend on it correctly.
    [#&#8203;30](https://togithub.com/pytest-dev/pytest-asyncio/issues/30)
-   Deal with the event loop policy by wrapping a special pytest hook,
    `pytest_fixture_setup`. This allows setting the policy before
    fixtures dependent on the `event_loop` fixture run, thus allowing
    them to take advantage of the `forbid_global_loop` parameter. As a
    consequence of this, we now depend on pytest 3.0.
    [#&#8203;29](https://togithub.com/pytest-dev/pytest-asyncio/issues/29)

## 0.4.1 (2016-06-01)

-   Fix a bug preventing the propagation of exceptions from the plugin.
    [#&#8203;25](https://togithub.com/pytest-dev/pytest-asyncio/issues/25)

## 0.4.0 (2016-05-30)

-   Make `event_loop` fixtures simpler to override by closing them in
    the plugin, instead of directly in the fixture.
    [#&#8203;21](https://togithub.com/pytest-dev/pytest-asyncio/pull/21)
-   Introduce the `forbid_global_loop` parameter.
    [#&#8203;21](https://togithub.com/pytest-dev/pytest-asyncio/pull/21)

## 0.3.0 (2015-12-19)

-   Support for Python 3.5 `async`/`await` syntax.
    [#&#8203;17](https://togithub.com/pytest-dev/pytest-asyncio/pull/17)

## 0.2.0 (2015-08-01)

-   `unused_tcp_port_factory` fixture.
    [#&#8203;10](https://togithub.com/pytest-dev/pytest-asyncio/issues/10)

## 0.1.1 (2015-04-23)

Initial release.

# Contributing

Contributions are very welcome. Tests can be run with `tox`, please
ensure the coverage at least stays the same before you submit a pull
request.

### [`v0.18.0`](https://togithub.com/pytest-dev/pytest-asyncio/releases/v0.18.0)

[Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.17.2...v0.18.0)

***

## title: 'pytest-asyncio: pytest support for asyncio'

[![image](https://img.shields.io/pypi/v/pytest-asyncio.svg)](https://pypi.python.org/pypi/pytest-asyncio)

[![image](https://togithub.com/pytest-dev/pytest-asyncio/workflows/CI/badge.svg)](https://togithub.com/pytest-dev/pytest-asyncio/actions?workflow=CI)

[![image](https://codecov.io/gh/pytest-dev/pytest-asyncio/branch/master/graph/badge.svg)](https://codecov.io/gh/pytest-dev/pytest-asyncio)

[![Supported Python versions](https://img.shields.io/pypi/pyversions/pytest-asyncio.svg)](https://togithub.com/pytest-dev/pytest-asyncio)

[![image](https://img.shields.io/badge/code%20style-black-000000.svg)](https://togithub.com/ambv/black)

pytest-asyncio is an Apache2 licensed library, written in Python, for
testing asyncio code with pytest.

asyncio code is usually written in the form of coroutines, which makes
it slightly more difficult to test using normal testing tools.
pytest-asyncio provides useful fixtures and markers to make testing
easier.

```{.sourceCode .python}
@&#8203;pytest.mark.asyncio
async def test_some_asyncio_code():
    res = await library.do_something()
    assert b"expected result" == res
```

pytest-asyncio has been strongly influenced by
[pytest-tornado](https://togithub.com/eugeniy/pytest-tornado).

# Features

-   fixtures for creating and injecting versions of the asyncio event
    loop
-   fixtures for injecting unused tcp/udp ports
-   pytest markers for treating tests as asyncio coroutines
-   easy testing with non-default event loops
-   support for \[async def]{.title-ref} fixtures and async generator
    fixtures
-   support *auto* mode to handle all async fixtures and tests
    automatically by asyncio; provide *strict* mode if a test suite
    should work with different async frameworks simultaneously, e.g.
    `asyncio` and `trio`.

# Installation

To install pytest-asyncio, simply:

```{.sourceCode .bash}
$ pip install pytest-asyncio
```

This is enough for pytest to pick up pytest-asyncio.

# Modes

Starting from `pytest-asyncio>=0.17`, three modes are provided: *auto*,
*strict* and *legacy* (default).

The mode can be set by `asyncio_mode` configuration option in
[configuration
file](https://docs.pytest.org/en/latest/reference/customize.html):

```{.sourceCode .ini}
### pytest.ini
[pytest]
asyncio_mode = auto
```

The value can be overriden by command-line option for `pytest`
invocation:

```{.sourceCode .bash}
$ pytest tests --asyncio-mode=strict
```

## Auto mode

When the mode is auto, all discovered *async* tests are considered
*asyncio-driven* even if they have no `@pytest.mark.asyncio` marker.

All async fixtures are considered *asyncio-driven* as well, even if they
are decorated with a regular `@pytest.fixture` decorator instead of
dedicated `@pytest_asyncio.fixture` counterpart.

*asyncio-driven* means that tests and fixtures are executed by
`pytest-asyncio` plugin.

This mode requires the simplest tests and fixtures configuration and is
recommended for default usage *unless* the same project and its test
suite should execute tests from different async frameworks, e.g.
`asyncio` and `trio`. In this case, auto-handling can break tests
designed for other framework; plase use *strict* mode instead.

## Strict mode

Strict mode enforces `@pytest.mark.asyncio` and
`@pytest_asyncio.fixture` usage. Without these markers, tests and
fixtures are not considered as *asyncio-driven*, other pytest plugin can
handle them.

Please use this mode if multiple async frameworks should be combined in
the same test suite.

## Legacy mode

This mode follows rules used by `pytest-asyncio<0.17`: tests are not
auto-marked but fixtures are.

This mode is used by default for the sake of backward compatibility,
deprecation warnings are emitted with suggestion to either switching to
`auto` mode or using `strict` mode with `@pytest_asyncio.fixture`
decorators.

In future, the default will be changed.

# Fixtures

## `event_loop`

Creates and injects a new instance of the default asyncio event loop. By
default, the loop will be closed at the end of the test (i.e. the
default fixture scope is `function`).

Note that just using the `event_loop` fixture won't make your test
function a coroutine. You'll need to interact with the event loop
directly, using methods like `event_loop.run_until_complete`. See the
`pytest.mark.asyncio` marker for treating test functions like
coroutines.

Simply using this fixture will not set the generated event loop as the
default asyncio event loop, or change the asyncio event loop policy in
any way. Use `pytest.mark.asyncio` for this purpose.

```{.sourceCode .python}
def test_http_client(event_loop):
    url = "http://httpbin.org/get"
    resp = event_loop.run_until_complete(http_client(url))
    assert b"HTTP/1.1 200 OK" in resp
```

This fixture can be easily overridden in any of the standard pytest
locations (e.g. directly in the test file, or in `conftest.py`) to use a
non-default event loop. This will take effect even if you're using the
`pytest.mark.asyncio` marker and not the `event_loop` fixture directly.

```{.sourceCode .python}
@&#8203;pytest.fixture
def event_loop():
    loop = MyCustomLoop()
    yield loop
    loop.close()
```

If the `pytest.mark.asyncio` marker is applied, a pytest hook will
ensure the produced loop is set as the default global loop. Fixtures
depending on the `event_loop` fixture can expect the policy to be
properly modified when they run.

## `unused_tcp_port`

Finds and yields a single unused TCP port on the localhost interface.
Useful for binding temporary test servers.

## `unused_tcp_port_factory`

A callable which returns a different unused TCP port each invocation.
Useful when several unused TCP ports are required in a test.

```{.sourceCode .python}
def a_test(unused_tcp_port_factory):
    port1, port2 = unused_tcp_port_factory(), unused_tcp_port_factory()
    ...
```

## `unused_udp_port` and `unused_udp_port_factory`

Work just like their TCP counterparts but return unused UDP ports.

## Async fixtures

Asynchronous fixtures are defined just like ordinary pytest fixtures,
except they should be decorated with `@pytest_asyncio.fixture`.

```{.sourceCode .python3}
import pytest_asyncio

@&#8203;pytest_asyncio.fixture
async def async_gen_fixture():
    await asyncio.sleep(0.1)
    yield "a value"

@&#8203;pytest_asyncio.fixture(scope="module")
async def async_fixture():
    return await asyncio.sleep(0.1)
```

All scopes are supported, but if you use a non-function scope you will
need to redefine the `event_loop` fixture to have the same or broader
scope. Async fixtures need the event loop, and so must have the same or
narrower scope than the `event_loop` fixture.

*auto* and *legacy* mode automatically converts async fixtures declared
with the standard `@pytest.fixture` decorator to *asyncio-driven*
versions.

# Markers

## `pytest.mark.asyncio`

Mark your test coroutine with this marker and pytest will execute it as
an asyncio task using the event loop provided by the `event_loop`
fixture. See the introductory section for an example.

The event loop used can be overridden by overriding the `event_loop`
fixture (see above).

In order to make your test code a little more concise, the pytest
`pytestmark`\_ feature can be used to mark entire modules or classes
with this marker. Only test coroutines will be affected (by default,
coroutines prefixed by `test_`), so, for example, fixtures are safe to
define.

```{.sourceCode .python}
import asyncio

import pytest
### All test coroutines will be treated as marked.
pytestmark = pytest.mark.asyncio

async def test_example(event_loop):
    """No marker!"""
    await asyncio.sleep(0, loop=event_loop)
```

In *auto* mode, the `pytest.mark.asyncio` marker can be omitted, the
marker is added automatically to *async* test functions.

# Note about unittest

Test classes subclassing the standard
[unittest](https://docs.python.org/3/library/unittest.html) library are
not supported, users are recommended to use
[unitest.IsolatedAsyncioTestCase](https://docs.python.org/3/library/unittest.html#unittest.IsolatedAsyncioTestCase)
or an async framework such as
[asynctest](https://asynctest.readthedocs.io/en/latest).

# Changelog

## 0.18.0 (22-02-07)

-   Raise a warning if [@&#8203;pytest](https://togithub.com/pytest).mark.asyncio is applied to non-async
    function.
    [#&#8203;275](https://togithub.com/pytest-dev/pytest-asyncio/issues/275)
-   Support parametrized `event_loop` fixture.
    [#&#8203;278](https://togithub.com/pytest-dev/pytest-asyncio/issues/278)

## 0.17.2 (22-01-17)

-   Require `typing-extensions` on Python<3.8 only.
    [#&#8203;269](https://togithub.com/pytest-dev/pytest-asyncio/issues/269)
-   Fix a regression in tests collection introduced by 0.17.1, the
    plugin works fine with non-python tests again.
    [#&#8203;267](https://togithub.com/pytest-dev/pytest-asyncio/issues/267)

## 0.17.1 (22-01-16)

-   Fixes a bug that prevents async Hypothesis tests from working
    without explicit `asyncio` marker when `--asyncio-mode=auto` is set.
    [#&#8203;258](https://togithub.com/pytest-dev/pytest-asyncio/issues/258)
-   Fixed a bug that closes the default event loop if the loop doesn't
    exist
    [#&#8203;257](https://togithub.com/pytest-dev/pytest-asyncio/issues/257)
-   Added type annotations.
    [#&#8203;198](https://togithub.com/pytest-dev/pytest-asyncio/issues/198)
-   Show asyncio mode in pytest report headers.
    [#&#8203;266](https://togithub.com/pytest-dev/pytest-asyncio/issues/266)
-   Relax `asyncio_mode` type definition; it allows to support pytest
    6.1+.
    [#&#8203;262](https://togithub.com/pytest-dev/pytest-asyncio/issues/262)

## 0.17.0 (22-01-13)

-   \[pytest-asyncio]{.title-ref} no longer alters existing event loop
    policies.
    [#&#8203;168](https://togithub.com/pytest-dev/pytest-asyncio/issues/168),
    [#&#8203;188](https://togithub.com/pytest-dev/pytest-asyncio/issues/168)
-   Drop support for Python 3.6
-   Fixed an issue when pytest-asyncio was used in combination with
    \[flaky]{.title-ref} or inherited asynchronous Hypothesis tests.
    [#&#8203;178](https://togithub.com/pytest-dev/pytest-asyncio/issues/178)
    [#&#8203;231](https://togithub.com/pytest-dev/pytest-asyncio/issues/231)
-   Added [flaky](https://pypi.org/project/flaky/) to test dependencies
-   Added `unused_udp_port` and `unused_udp_port_factory` fixtures
    (similar to `unused_tcp_port` and `unused_tcp_port_factory`
    counterparts.
    [#&#8203;99](https://togithub.com/pytest-dev/pytest-asyncio/issues/99)
-   Added the plugin modes: *strict*, *auto*, and *legacy*. See
    [documentation](https://togithub.com/pytest-dev/pytest-asyncio#modes)
    for details.
    [#&#8203;125](https://togithub.com/pytest-dev/pytest-asyncio/issues/125)
-   Correctly process `KeyboardInterrupt` during async fixture setup
    phase
    [#&#8203;219](https://togithub.com/pytest-dev/pytest-asyncio/issues/219)

## 0.16.0 (2021-10-16)

-   Add support for Python 3.10

## 0.15.1 (2021-04-22)

-   Hotfix for errors while closing event loops while replacing them.
    [#&#8203;209](https://togithub.com/pytest-dev/pytest-asyncio/issues/209)
    [#&#8203;210](https://togithub.com/pytest-dev/pytest-asyncio/issues/210)

## 0.15.0 (2021-04-19)

-   Add support for Python 3.9
-   Abandon support for Python 3.5. If you still require support for
    Python 3.5, please use pytest-asyncio v0.14 or earlier.
-   Set `unused_tcp_port_factory` fixture scope to 'session'.
    [#&#8203;163](https://togithub.com/pytest-dev/pytest-asyncio/pull/163)
-   Properly close event loops when replacing them.
    [#&#8203;208](https://togithub.com/pytest-dev/pytest-asyncio/issues/208)

## 0.14.0 (2020-06-24)

-   Fix
    [#&#8203;162](https://togithub.com/pytest-dev/pytest-asyncio/issues/162),
    and `event_loop` fixture behavior now is coherent on all scopes.
    [#&#8203;164](https://togithub.com/pytest-dev/pytest-asyncio/pull/164)

## 0.12.0 (2020-05-04)

-   Run the event loop fixture as soon as possible. This helps with
    fixtures that have an implicit dependency on the event loop.
    [#&#8203;156](https://togithub.com/pytest-dev/pytest-asyncio/pull/156)

## 0.11.0 (2020-04-20)

-   Test on 3.8, drop 3.3 and 3.4. Stick to 0.10 for these versions.
    [#&#8203;152](https://togithub.com/pytest-dev/pytest-asyncio/pull/152)
-   Use the new Pytest 5.4.0 Function API. We therefore depend on
    pytest >= 5.4.0.
    [#&#8203;142](https://togithub.com/pytest-dev/pytest-asyncio/pull/142)
-   Better `pytest.skip` support.
    [#&#8203;126](https://togithub.com/pytest-dev/pytest-asyncio/pull/126)

## 0.10.0 (2019-01-08)

-   `pytest-asyncio` integrates with
    [Hypothesis](https://hypothesis.readthedocs.io) to support `@given`
    on async test functions using `asyncio`.
    [#&#8203;102](https://togithub.com/pytest-dev/pytest-asyncio/pull/102)
-   Pytest 4.1 support.
    [#&#8203;105](https://togithub.com/pytest-dev/pytest-asyncio/pull/105)

## 0.9.0 (2018-07-28)

-   Python 3.7 support.
-   Remove `event_loop_process_pool` fixture and
    `pytest.mark.asyncio_process_pool` marker (see
    <https://bugs.python.org/issue34075> for deprecation and removal
    details)

## 0.8.0 (2017-09-23)

-   Improve integration with other packages (like aiohttp) with more
    careful event loop handling.
    [#&#8203;64](https://togithub.com/pytest-dev/pytest-asyncio/pull/64)

## 0.7.0 (2017-09-08)

-   Python versions pre-3.6 can use the async_generator library for
    async fixtures. \[[#&#8203;62](https://togithub.com/pytest-dev/pytest-asyncio/issues/62)
 [https://github.com/pytest-dev/pytest-asyncio/pull/62](https://togithub.com/pytest-dev/pytest-asyncio/pull/62)ll/62>]{.title-ref}

## 0.6.0 (2017-05-28)

-   Support for Python versions pre-3.5 has been dropped.
-   `pytestmark` now works on both module and class level.
-   The `forbid_global_loop` parameter has been removed.
-   Support for async and async gen fixtures has been added.
    [#&#8203;45](https://togithub.com/pytest-dev/pytest-asyncio/pull/45)
-   The deprecation warning regarding `asyncio.async()` has been fixed.
    [#&#8203;51](https://togithub.com/pytest-dev/pytest-asyncio/pull/51)

## 0.5.0 (2016-09-07)

-   Introduced a changelog.
    [#&#8203;31](https://togithub.com/pytest-dev/pytest-asyncio/issues/31)
-   The `event_loop` fixture is again responsible for closing itself.
    This makes the fixture slightly harder to correctly override, but
    enables other fixtures to depend on it correctly.
    [#&#8203;30](https://togithub.com/pytest-dev/pytest-asyncio/issues/30)
-   Deal with the event loop policy by wrapping a special pytest hook,
    `pytest_fixture_setup`. This allows setting the policy before
    fixtures dependent on the `event_loop` fixture run, thus allowing
    them to take advantage of the `forbid_global_loop` parameter. As a
    consequence of this, we now depend on pytest 3.0.
    [#&#8203;29](https://togithub.com/pytest-dev/pytest-asyncio/issues/29)

## 0.4.1 (2016-06-01)

-   Fix a bug preventing the propagation of exceptions from the plugin.
    [#&#8203;25](https://togithub.com/pytest-dev/pytest-asyncio/issues/25)

## 0.4.0 (2016-05-30)

-   Make `event_loop` fixtures simpler to override by closing them in
    the plugin, instead of directly in the fixture.
    [#&#8203;21](https://togithub.com/pytest-dev/pytest-asyncio/pull/21)
-   Introduce the `forbid_global_loop` parameter.
    [#&#8203;21](https://togithub.com/pytest-dev/pytest-asyncio/pull/21)

## 0.3.0 (2015-12-19)

-   Support for Python 3.5 `async`/`await` syntax.
    [#&#8203;17](https://togithub.com/pytest-dev/pytest-asyncio/pull/17)

## 0.2.0 (2015-08-01)

-   `unused_tcp_port_factory` fixture.
    [#&#8203;10](https://togithub.com/pytest-dev/pytest-asyncio/issues/10)

## 0.1.1 (2015-04-23)

Initial release.

# Contributing

Contributions are very welcome. Tests can be run with `tox`, please
ensure the coverage at least stays the same before you submit a pull
request.

</details>

---

### Configuration

📅 **Schedule**: At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#github/allenporter/rtsp-to-webrtc-client).


Discussion / hints:

Fix patch:
diff --git a/requirements.txt b/requirements.txt
index 7920e86..b56b498 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -29,9 +29,9 @@ pyflakes==2.4.0
 pyparsing==3.0.7
 pytest==6.2.5
 pytest-aiohttp==0.3.0
-pytest-asyncio==0.16.0
+pytest-asyncio==0.17.2
 pytest-cov==3.0.0
-pytest-mock==3.6.1
+pytest-mock==3.7.0
 regex==2022.1.18
 six==1.16.0
 toml==0.10.2


Test patch:
diff --git a/pytest.ini b/pytest.ini
index 52be6a9..9edc52c 100644
--- a/pytest.ini
+++ b/pytest.ini
@@ -1,2 +1,3 @@
 [pytest]
 log_level = DEBUG
+asyncio_mode = auto
diff --git a/tests/conftest.py b/tests/conftest.py
index 71f8be4..c8064b0 100644
--- a/tests/conftest.py
+++ b/tests/conftest.py
@@ -2,7 +2,7 @@
 
 import logging
 from collections.abc import Awaitable, Callable, Generator
-from typing import cast
+from typing import cast, Any
 
 import aiohttp
 import pytest
@@ -13,6 +13,11 @@
 _LOGGER = logging.getLogger(__name__)
 
 
+@pytest.fixture
+def loop(event_loop: Any) -> Any:
+    return event_loop
+
+
 async def handler(request: aiohttp.web.Request) -> aiohttp.web.Response:
     """Handles the request, inserting response prepared by tests."""
     if request.method == "POST":
diff --git a/tests/test_web_client.py b/tests/test_web_client.py
index 3ead05c..f61f78a 100644
--- a/tests/test_web_client.py
+++ b/tests/test_web_client.py
@@ -340,12 +340,12 @@ async def test_server_failure_with_error(cli: TestClient) -> None:
 async def test_heartbeat(cli: TestClient) -> None:
     """Test successful response from RTSPtoWebRTC server."""
     assert isinstance(cli.server, TestServer)
-    cli.server.app["response"] = [
+    cli.server.app["response"].extend([
         aiohttp.web.Response(status=200),
         aiohttp.web.Response(status=502),
         aiohttp.web.Response(status=404),
         aiohttp.web.Response(status=200),
-    ]
+    ])
 
     client = WebClient(cast(ClientSession, cli))
 
diff --git a/tests/test_webrtc_client.py b/tests/test_webrtc_client.py
index 5b762ed..edbc41d 100644
--- a/tests/test_webrtc_client.py
+++ b/tests/test_webrtc_client.py
@@ -86,12 +86,12 @@ async def test_server_failure_with_error(cli: TestClient) -> None:
 async def test_heartbeat(cli: TestClient) -> None:
     """Test successful response from RTSPtoWebRTC server."""
     assert isinstance(cli.server, TestServer)
-    cli.server.app["response"] = [
+    cli.server.app["response"].extend([
         aiohttp.web.Response(status=200),
         aiohttp.web.Response(status=502),
         aiohttp.web.Response(status=404),
         aiohttp.web.Response(status=200),
-    ]
+    ])
 
     client = Client(cast(ClientSession, cli))