Schedulers.immediate() in tests limits capabilities

[artemik]

For tests, Schedulers.immediate() is used instead of Schedulers.io() and Schedulers.mainThread(). It makes impossible to test that repoListPresenter.onSearchButtonClick() doesn't call view.hideLoading() until it loads result from the model.

The current RepoListPresenterTest.testShowLoading() show look like this:

@Test
public void testShowLoading() {
	repoListPresenter.onSearchButtonClick();

	verify(mockView).showLoading();
	verify(mockView, never()).hideLoading();
}

But it's impossible now. Invocation of repoListPresenter.onSearchButtonClick() is blocking and will trigger view.hideLoading() upon completion.

[andrey7mel]

Thank you! I fix this)

Суббота, 26 ноября 2016, 14:15 +04:00 от Artem ***@***.***>: For tests, Schedulers.immediate() is used instead of Schedulers.io() and Schedulers.mainThread(). It makes impossible to test that repoListPresenter.onSearchButtonClick() doesn't call view.hideLoading() until it loads result from the model. The current RepoListPresenterTest.testShowLoading() show look like this: @test

public void testShowLoading() { repoListPresenter.onSearchButtonClick(); verify(mockView).showLoading(); verify(mockView, never()).hideLoading(); }

…

But it's impossible now. Invocation of repoListPresenter.onSearchButtonClick() is blocking and will trigger view.hideLoading() upon completion. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or mute the thread .

--------------------------------------------------------------- Мельников Андрей