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 … Read more
Create a robolectric.properties file inside the app/src/test/resources directory with the following line: sdk=28 This will force Robolectric to use API 28 instead of 29.
I’m assuming you’re trying to run the tests with JUnit. You can try two different things: Create a Custom TestRunner class, as shown here. Check the CustomTestRunner section, where you basically create a TestRunner that actually knows the right manifest to use. Specify your tests for them to run with your test runner, with the … Read more
In Robolectric 2.1.1 you can verify if Intent starting new Activity was emitted in following way. @RunWith(RobolectricTestRunner.class) public class MyTest { private ShadowActivity shadowActivity; private MyActivity activity; @Before public void setup() { activity = new MyActivity(); shadowActivity = Robolectric.shadowOf(activity); } @Test public shouldStartNewActivityWhenSomething() { //Perform activity startup //Do some action which starts second activity, for … Read more
I would use Mockito to create a Mock of the interface and then pass that instance to your code in your tests. You could also manually create an implementation of that interface in your test code and use that. So you have to do the mocking yourself and it is important that the code you … Read more
As mentioned by an engineer from Google team (most possibly Xavier Ducrohet), Robolectric has issues with AAPT2: Robolectric is not compatible with aapt2. Two options here. First option – follow Robolectric guidelines for Android Studio 3.0+ Add the following to your build.gradle: android { testOptions { unitTests { includeAndroidResources = true } } } Annotate … Read more
Found out how – seems so obvious now! For those who are interested, you just get the sharedPreferences, and populate it with the required data. SharedPreferences sharedPreferences = ShadowPreferenceManager.getDefaultSharedPreferences(Robolectric.application.getApplicationContext()); sharedPreferences.edit().putString(“testId”, “12345”).commit(); If you have a custom SharedPreferences, you should be able to do this (haven’t really tested properly, but should also work) SharedPreferences sharedPreferences = … Read more
I am running robolectric-2.0-alpha-3. What worked for me was to set in the setUp method of my test the stream to stdout Something like: @Before public void setUp() throws Exception { ShadowLog.stream = System.out; //you other setup here } With this version of robolectric I had no success doing the same (ShadowLog.stream = System.out) in … Read more
It is generally not a good idea to test real server requests. See this blog post for an interesting discussion on the topic. According to the author, using your real server is a problem because: Another moving piece that can intermittently fail Requires some expertise outside of the Android domain to deploy the server and … Read more