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
I would like to know what is the benefit of using the RxSchedulersOverrideRule TestRule instead of the toBlocking? Is it only to avoid attaching toBlocking to every call in every test method? Or the possibility to run the tests on the JVM avoiding the RxAndroid Scheduler?
The text was updated successfully, but these errors were encountered:
I saw that you can bypass the package private without needing to rely on reflection using this trick shown at this link http://fedepaol.github.io/blog/2015/09/13/testing-rxjava-observables-subscriptions/ . This guy just creates a class with package name "rx.plugins" and delegates the method call to the now accessible package private method reset().
I would like to know what is the benefit of using the RxSchedulersOverrideRule TestRule instead of the toBlocking? Is it only to avoid attaching toBlocking to every call in every test method? Or the possibility to run the tests on the JVM avoiding the RxAndroid Scheduler?
The text was updated successfully, but these errors were encountered: