Matthew Farrellee 30b2e6a495 chore: default to pytest asyncio-mode=auto (#2730) ... # What does this PR do? previously, developers who ran `./scripts/unit-tests.sh` would get `asyncio-mode=auto`, which meant `@pytest.mark.asyncio` and `@pytest_asyncio.fixture` were redundent. developers who ran `pytest` directly would get pytest's default (strict mode), would run into errors leading them to add `@pytest.mark.asyncio` / `@pytest_asyncio.fixture` to their code. with this change - - `asyncio_mode=auto` is included in `pyproject.toml` making behavior consistent for all invocations of pytest - removes all redundant `@pytest_asyncio.fixture` and `@pytest.mark.asyncio` - for good measure, requires `pytest>=8.4` and `pytest-asyncio>=1.0` ## Test Plan - `./scripts/unit-tests.sh` - `uv run pytest tests/unit`		2025-07-11 13:00:24 -07:00
..
routers	chore: default to pytest asyncio-mode=auto (#2730)	2025-07-11 13:00:24 -07:00
test_build_path.py	feat: include run.yaml in the container image (#2005)	2025-04-24 11:29:53 +02:00
test_context.py	chore: default to pytest asyncio-mode=auto (#2730)	2025-07-11 13:00:24 -07:00
test_distribution.py	chore: enable pyupgrade fixes (#1806)	2025-05-01 14:23:50 -07:00