Unlike mocks, artificial implementations give us complete control of our dependencies in product tests, permitting us to precisely and carefully testing reactive flows.
At OkCupid, we often utilize the Mockito collection for producing mocks of our own dependencies used inside our JUnit assessments. This enables united states to quickly mock return beliefs for certain practices, or perhaps to confirm a method was known as on one in our dependencies, but it can provide problems while the integration amongst the part under test and the dependencies be more difficult.
On this page, we’re browsing walk through a limitation discover utilizing a mocking library, and go over the way we could get past that restriction simply by using our very own artificial execution. Let’s start by position the period for your difficulty.
Placing The Phase
Before we talk about the problem, let’s be certain that we see the component under examination. We’ll be looking at a ViewModel that is accountable for creating a system request and revealing some listings.
Down the page may be the snippet when it comes down to ViewModel, however, if you’d like to see the relevant tuition, there is all of them within this gist. Keep in mind that within ViewModel, when it is created, we request account ideas in the init way:
As soon as the ViewModel is generated, we’ll give off a running county to the LiveData. Next, we’ll request a profile, and publish another ProfileViewState if the phone call succeeds or fails.
This really is everything we want in regards to our component under test. Next we can test drive it.
Screening The ViewModel
We’ll start out with one good instance examination to make certain that as soon as we need a user, a running state try emitted accompanied by an information county.