TestClient support for use in testing suites, e.g. testing apis with pytest.

[y2kbugger]

In Winloop 0.2.0 or before 2026 I would like to start planning to migrate to pytest so that things could be formatted a little better. A Migration Python script might be needed or looked into.

One thing to consider is a tutorial on how to enable test clients to use Winloop

https://starlette.dev/testclient/

asyncio makes test suites so slow.

[Vizonex]

@y2kbugger I had decided for that to use pytest to activate the unittests. I need to make sure I go through the readme at somepoint since this plan has already been fulfilled and I planned to keep my tests somewhat 1:1 with uvloop.

About Further Migrations to Pytest

asyncio makes test suites so slow.

Not to try and discourage you or anybody else from trying to migrate the testsuite code any further, I think it would be great to have the current asyncio testsuite updated, however I do not have the encouragement to start migrations yet. If we did migrate fully to pytest what I would recommend doing is anyio+pytest as it is less annoying or stressful as pytest-asyncio or writing our own systems. I would also encourage that whatever you migrate on the winloop's-side should be reflected onto uvloop's side too. It would not only benefit us but also uvloop's end but like you mentioned from what I have quoted in your comment the current testsuite is sluggish and also slow as it takes around 4 - 5 minutes per run on each python version that is currently being supported.

However if we were to do a full migration to pytest, (that also means even the class types are no longer being derived out of unittest), there are still a few caveats and road barriers that I might need to explain to you.

• 1. uvloop which I choose to mirror for the sake of maintenance and sanity, currently has a possible road barrier with migrations to pytest. which are the following:
  • uvloop still is supporting old versions of python as far back as 3.8 When they choose to move is unknown I have already dropped 3.9 support over here rather recently for the sake of my own sanity in keeping up with newer releases of python but also incase of zero day vulnerabilities that may no longer receive additional maintenance.
  • pytest likewise has dropped support for these earlier versions that uvloop attempts to support but I could be wrong.
• 2. Some tests may require one or more eventloops are some tests may need to simulate shutting down the event loop or etc. These may not be able to become further optimized. Likewise the standard asnycio library is also tested because the uvloop maintainers want to ensure the library is 1 to 1 with asyncio.
• 3. While it may be safe to migrate to pytest on our end I bring up uvloop which is the related os sibling library because I also provide feedback at times on their end whenever changes are being made or when I have recommendations for them.

Other Ideas Workarounds That don't involve using our testsuite

If you decided to do any changes on your own without this I would recommend you to have a look at anyio+pytest like I have mentioned earlier it fully supports winloop by default when the backend option use_uvloop is set to true when the OS is windows.