fix: Update pytest-asyncio configuration for worker tests

- Changed asyncio_mode from "strict" to "auto" in pyproject.toml to fix worker fixture issues
- Updated testing documentation to explain asyncio configuration
- Fixed worker tests that were failing due to async generator handling

The auto mode allows for more flexible handling of async/sync code interactions, particularly in worker-related tests where we need to manage both synchronous and asynchronous operations.

Author: san-tekart

docs/testing.md

@@ -84,3 +84,12 @@ pytest --cov=tsignal
 # Generate HTML coverage report
 pytest --cov=tsignal --cov-report=html
 ```
+
+## Async Testing Configuration
+
+The project uses `pytest-asyncio` with `asyncio_mode = "auto"` to handle async fixtures and tests. This configuration allows for more flexible handling of async/sync code interactions, especially in worker-related tests where we need to manage both synchronous and asynchronous operations.
+
+Key points:
+- Async fixtures can yield values directly
+- Both sync and async tests can use the same fixtures
+- Worker thread initialization and cleanup are handled automatically

pyproject.toml

@@ -49,7 +49,7 @@ markers = [
     "asyncio: mark test as an async test",
     "performance: mark test as a performance test",
 ]
-asyncio_mode = "strict"
+asyncio_mode = "auto"
 asyncio_default_fixture_loop_scope = "function"
 
 [tool.coverage.run]