Skip to content

Use sync clients in respx transport tests#3020

Merged
adamtheturtle merged 1 commit intomainfrom
adamtheturtle/respx-async-test
Feb 25, 2026
Merged

Use sync clients in respx transport tests#3020
adamtheturtle merged 1 commit intomainfrom
adamtheturtle/respx-async-test

Conversation

@adamtheturtle
Copy link
Member

@adamtheturtle adamtheturtle commented Feb 25, 2026

Convert tests/mock_vws/test_respx_mock_usage.py from async vws clients to synchronous VWS, CloudRecoService, and VuMarkService usage. Inject HTTPXTransport() so the tests still exercise the respx/httpx interception path while removing asyncio.run, async with, and await. Verified with uv run --extra dev pytest tests/mock_vws/test_respx_mock_usage.py -q (5 passed).


Note

Low Risk
Test-only refactor switching from async to sync client APIs while keeping the same mocked HTTPX/respx interception path; low blast radius outside of potential test behavior differences (timeouts/context management).

Overview
Updates the MockVWS/respx transport tests to use synchronous vws clients (VWS, CloudRecoService, VuMarkService) instead of async variants.

Removes asyncio.run, async with, and await, and explicitly injects HTTPXTransport() so requests still flow through the httpx interception path while exercising the same timeout, base-URL-prefix, target lifecycle, query, and VuMark image generation scenarios.

Written by Cursor Bugbot for commit a96d77e. This will update automatically on new commits. Configure here.

@adamtheturtle adamtheturtle merged commit 7b2a303 into main Feb 25, 2026
104 checks passed
@adamtheturtle adamtheturtle deleted the adamtheturtle/respx-async-test branch February 25, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant