You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, TestClock requires manual time adjustments, making it cumbersome for testing complex asynchronous scenarios involving multiple parallel processes with varying delays.
What is the feature you are proposing to solve the problem?
Enhance TestClock with automatic time management, similar to RxJS's VirtualTimeScheduler. This scheduler should have a flush() method that executes all queued actions and advances time accordingly. This feature would help create more realistic and comprehensive test scenarios without the need to manually simulate each time step.
What alternatives have you considered?
I considered using Clock.sleeps() to obtain the next scheduled event and then adjusting time to it manually. However, I could only retrieve an empty array during my tests. Maybe i did something wrong
The text was updated successfully, but these errors were encountered:
What is the problem this feature would solve?
Currently, TestClock requires manual time adjustments, making it cumbersome for testing complex asynchronous scenarios involving multiple parallel processes with varying delays.
What is the feature you are proposing to solve the problem?
Enhance
TestClock
with automatic time management, similar to RxJS's VirtualTimeScheduler. This scheduler should have a flush() method that executes all queued actions and advances time accordingly. This feature would help create more realistic and comprehensive test scenarios without the need to manually simulate each time step.What alternatives have you considered?
I considered using Clock.sleeps() to obtain the next scheduled event and then adjusting time to it manually. However, I could only retrieve an empty array during my tests. Maybe i did something wrong
The text was updated successfully, but these errors were encountered: