ExplicitlyTriggeredScheduler
Related Doc:
package testkit
Advance the clock by the specified duration, executing all outstanding jobs on the calling thread before returning.
Advance the clock by the specified duration, executing all outstanding jobs on the calling thread before returning.
We will not add a dilation factor to this amount, since the scheduler API also does not apply dilation. If you want the amount of time passed to be dilated, apply the dilation before passing the delay to this method.
For testing: scheduler that does not look at the clock, but must be progressed manually by calling
timePasses.This allows for faster and less timing-sensitive specs, as jobs will be executed on the test thread instead of using the original {ExecutionContext}. This means recreating specific scenario's becomes easier, but these tests might fail to catch race conditions that only happen when tasks are scheduled in parallel in 'real time'.