Testing and Time and Concurrency With Rx.NET Schedulers
summary
Demo shows how Rx.NET Schedulers and a Virtual Time TestScheduler let code and tests treat time as controllable values. A search UI uses throttle 500ms and minimum 3 characters rules, operators like Switch and DistinctUntilChanged, and a mock search client (NSubstitute) so slow and fast responses are reproducible. Tests advance the virtual clock to assert only the latest result appears and run instantly with no real waiting, proving the approach works.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:45About Tamir
- 2:14Reactive Extension
- 4:00Example
- 6:09Reactive Extensions
- 6:43Observable
- 8:19Observable and Observer
- 10:36Error
- 11:11Reactive Expansion
- 11:44Observable Messages
- 14:23Creating Observable
- 16:37Reactive Extension Operators
- 17:13Reactive Extension Example
- 19:32Fiddler
- 20:43Code
- 25:10Project Scheduler
- 25:40Project Scheduler Interface
- 27:16Time
- 28:16Test Cases
- 28:58Questions
- 29:38Test Scheduler
- 30:06SearchViewModel
- 30:49ViewModel
- 31:26Search Client
- 31:45Test Case
- 33:03concurrency is types
- 33:23concurrency provider
- 33:53testing
- 37:28summary
related talks
38mCuring your event processing blues with Rx
38mRx.NET, from the inside out
38mBending time with Schedulers and RxJS 5
45mUnit testing patterns for Concurrent code
16mIntroduction to Marble Testing Rx (Web, iOS, Android)
30mRxJS schedulers in depth
32mVenturing Into the world of RxSwift unit testing
56mAlgorithm Design For Values Distributed In Time