RxJava如何测试去抖?

时间:2019-02-12 12:01:52

标签: android junit rx-java debounce

我正在尝试在Android中测试RxJava2的“反跳”运算符。

我为搜索功能使用了“反跳”运算符。

在视图(活动)中,开始搜索。

etSearch.addTextChangedListener(object : TextWatcher {

    override fun afterTextChanged(editable: Editable) {
        mPresenter.search(editable.toString())
    }

    ...
})

主持人在这里:

class MyPresenter(
    private val view: MyContract.View,
    private val apiService: ApiServie = ApiServiceImpl(),
    private val searchSubject: PublishSubject<String> = PublishSubject.create(),
    var debounceScheduler: Scheduler = Schedulers.computation()
) : MyContract.Presenter {

    init {
        setupSearch()
    }

    override fun search(keyword: String) {
        if (searchDisposable.size() == 0) {
            setupSearch()
        }

        searchSubject.onNext(keyword)
    }

    private fun setupSearch() {
        searchSubject.debounce(1000, TimeUnit.MILLISECONDS, debounceScheduler)
                .distinctUntilChanged()
                .switchMap { keyword ->
                    apiService.search(keyword)
                }
                .subscribeOn(Schedulers.io())
                .observeOn(AndroidSchedulers.mainThread())
                .subscribe { response ->
                    response.data?.let { data ->
                        view.searchResult(data)
                    }
                }
    }
}

实际上,当我进行集成测试时,它可以正常工作。 但是我要做的是测试MyPresenter类的“搜索”功能。

为此,我读了article

但这不起作用...

我的测试代码在这里:

class MyTest {

    @Mock
    private lateinit var mockView: MyContract.View

    @Mock
    private lateinit var mockApiService: ApiService

    private lateinit var mMyPresenter: MyPresenter

    private lateinit var inOrder: InOrder

    private val mTestScheduler: TestScheduler = TestScheduler()

    private val ZERO = 0

    private fun setUpScheduler() {
        val immediate = object : Scheduler() {
            override fun createWorker() = ExecutorScheduler.ExecutorWorker(Runnable::run)
        }

        RxJavaPlugins.setInitIoSchedulerHandler { immediate }
        RxAndroidPlugins.setInitMainThreadSchedulerHandler { immediate }
    }

    @Before
    fun setup() {
        MockitoAnnotations.initMocks(this)
        setUpScheduler()

        mMyPresenter = MyPresenter(mockView, mockApiService)

        inOrder = inOrder(mockView)
    }

    @Test
    fun searchBillsTest() {
        `when`(mockApiService.search("America"))
                .thenReturn(Observable.just(mockResult))

        mMyPresenter.debounceScheduler = mTestScheduler

        mMyPresenter.search("America")
        mTestScheduler.advanceTimeBy(1000, TimeUnit.MILLISECONDS)

        verify(mockView).searchResult(mockResult)
    }
}

未调用最后一个验证... 我不知道为什么 我添加了“ doOnNext”来打印日志以在“ searchSubject”中找到原因,但是“ doOnNext”没有被调用... “ doOnSubscribe”被称为...

请你知道为什么吗?

1 个答案:

答案 0 :(得分:1)

为了尽快通过测试代码,只需更改一些内容即可。

  1. 使用TestScheduler
  2. 划分uiio调度程序。
  3. 在触发主题触发事件之前使用Scheduler.triggerActions
@RunWith(MockitoJUnitRunner::class)
class DebounceTest {
    private lateinit var searchSubject: PublishSubject<String>

    @Mock lateinit var apiService: ApiService

    @Mock lateinit var presenter: Presenter

    private lateinit var disposable: Disposable

    private lateinit var ioTestScheduler: TestScheduler
    private lateinit var uiTestScheduler: TestScheduler

    @Before fun setUp() {
        searchSubject = PublishSubject.create<String>()

        ioTestScheduler = TestScheduler()
        uiTestScheduler = TestScheduler()

        setupSearch(uiTestScheduler, ioTestScheduler)

        // important https://stackoverflow.com/a/53543257/1355048
        ioTestScheduler.triggerActions()
    }

    @After fun tearDown() {
        disposable.dispose()
    }

    @Test fun searchBillsTest() {
        `when`(apiService.search("America")).thenReturn(Observable.just("MOCK RESULT"))

        searchSubject.onNext("America")

        ioTestScheduler.advanceTimeBy(1, TimeUnit.SECONDS)
        uiTestScheduler.triggerActions()

        verify(presenter).doSomething("MOCK RESULT")
    }

    private fun setupSearch(uiScheduler: Scheduler, ioScheduler: Scheduler) {
        disposable = searchSubject.debounce(1, TimeUnit.SECONDS, ioScheduler)
                .distinctUntilChanged()
                .switchMap { apiService.search(it) }
                .subscribeOn(ioScheduler)
                .observeOn(uiScheduler)
                .subscribe { response ->
                    presenter.doSomething(response)
                }
    }

    interface ApiService {
        fun search(query: String): Observable<String>
    }

    interface Presenter {
        fun doSomething(result: String)
    }
}