Book Image

Reactive Programming in Kotlin

By : Rivu Chakraborty
Book Image

Reactive Programming in Kotlin

By: Rivu Chakraborty

Overview of this book

In today's app-driven era, when programs are asynchronous, and responsiveness is so vital, reactive programming can help you write code that's more reliable, easier to scale, and better-performing. Reactive programming is revolutionary. With this practical book, Kotlin developers will first learn how to view problems in the reactive way, and then build programs that leverage the best features of this exciting new programming paradigm. You will begin with the general concepts of Reactive programming and then gradually move on to working with asynchronous data streams. You will dive into advanced techniques such as manipulating time in data-flow, customizing operators and provider and how to use the concurrency model to control asynchronicity of code and process event handlers effectively. You will then be introduced to functional reactive programming and will learn to apply FRP in practical use cases in Kotlin. This book will also take you one step forward by introducing you to Spring 5 and Spring Boot 2 using Kotlin. By the end of the book, you will be able to build real-world applications with reactive user interfaces as well as you'll learn to implement reactive programming paradigms in Android.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Dedication
Preface

Understanding TestScheduler


Think of an Observable/Flowable created with the Observable.interval() / Flowable.interval() factory method. If you have given a long interval (say five minutes) in them and have tested at least say 100 emissions then it would take a long time for testing to complete (500 minutes = 8.3 hours, that is, a complete man-hour just to test a single producer). Now if you have more producers like that with a larger interval and more emissions to test then it would probably take the whole lifetime to test, when would you ship the product then?

TestScheduler is here to save your life. They can effectively simulate time with time-driven producers so that we can do assertions by fast-forwarding it by a specific amount.

So, the following is the respective implementation:

    @Test 
    fun `test by fast forwarding time`() { 
      val testScheduler = TestScheduler() 
 
      val observable = 
      Observable.interval(5,TimeUnit.MINUTES,testScheduler) 
      val testObserver...