-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Event-Loop fixture that does not automatically advance time #95
Comments
#83 seems similar to what you want |
Thanks @albertodonato , I've been working on this for a bit now and #110 is the most recent set of commits to achieve this behavior in case you are interested. |
Looking at your fixture in #83 is very interesting. #110 (and the original #96) takes a different approach, changing the loop class to give all |
Along with the inspiration from Twisted, consider Trio as well. https://pytest-trio.readthedocs.io/en/stable/reference.html#autojump_clock Advancing time automatically even faster than the wall clock is very useful as well. |
It would be ideal to add an additional
clock_event_loop
fixture with a customAbstractEventLoop
. Instead, this one would only advance time explicitly similar to thetwisted.internet.task.Clock
useful for testingtwisted
reactors. This would allow for tests to advance time and test time-based features to verify that they are correctly running when expected without having to wait for time to progress. If there is a different way to achieve this goal, I would appreciate the advice if I missed something.The text was updated successfully, but these errors were encountered: