Menu
This is first time I have to write unit test cases in Android.
So I have searched lots of things.
So I have some doubts in Robolectric & Mokito.
I have search for difference between Mokito & Robolectric but don't get any proper answer for that.
Please suggest.
911
This is in contrast to using pure Mockito, which often ends up with tests that are the reverse of the logic you are attempting to test. Robolectric works by emulating the native calls the SDK would make on Dalvik, but on the JVM, so it can run much, much faster. This makes full unit testing and TDD possible.
JUnit is a framework that helps with writing and running your unit tests. Mockito (or any other mocking tool) is a framework that you specifically use to efficiently write certain kind of tests.
unit tests can be written under test java package, and instrumental tests can be written under androidTest package. You can then access UI widgets using Espresso ViewMatchers and then you can apply actions on them using ViewActions . Check documentation for further help. Show activity on this post.
They have slightly different usages and I tend to use both in my projects.
Mockito
is used for making mocks of your classes.
When you are testing a particular class you mock all of its dependencies with Mockito.
Where possible most of your tests should use mockito. To make this possible most people split their code up into MVP, etc where the business logic is separated from the View logic. This way your business logic (Presenter) has no knowledge (or dependencies) on the Android library and has no need to have mocks of them.
Robolectric
is a library which contains many mocks of Android classes.
The Robolectric test runner injects these 'shadow objects' in place of the actual Android classes when the tests are run. This is what allows the tests to run on the JVM without booting up an instance of Android.
When using MVP your View layer tends to be implemented by the Activity/Fragment and this is where you can use Robolectric to mock these.
Notes
Use Robolectric only where necessary. It basically re-implements parts of the Android framework but not always in exactly the same way.
You may also need another library such as PowerMock. This allows the mocking of static classes such as Math or can be used to mock static Android classes such as TextUtils.
Both are used with JUnit
66
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
