Robolectric and IntentServices

Question

Using Robolectric, how would one go about testing an IntentService that broadcasts intents as a response?

Assuming the following class:

class MyService extends IntentService {
    @Override
    protected void onHandleIntent(Intent intent) {
        LocalBroadcastManager.getInstance(this).sendBroadcast(new Intent("action"));
    }
}

In my test case, I'm attempting to do something like this:

@RunWith(RobolectricTestRunner.class)
public class MyServiceTest{
    @Test
    public void testPurchaseHappyPath() throws Exception {

        Context context = new Activity();

        // register broadcast receiver
        BroadcastReceiver br = new BroadcastReceiver() {

            @Override
            public void onReceive(Context context, Intent intent) {
                // test logic to ensure that this is called
            }

        };
        context.registerReceiver(br, new IntentFilter("action"));

        // This doesn't work
        context.startService(new Intent(context, MyService.class));

    }

}

MyService is never started using this approach. I'm relatively new to Robolectric, so I'm probably missing something obvious. Is there some sort of binding I have to do before calling startService? I've verified that broadcasting works by just calling sendBroadcast on the context. Any ideas?

I don´t have a concrete solution for you but i think that you have to mock the broadcast receiver with mockito to be able to call onReceive within you code. Or the easier way would be to extract the logic from onReceive into a separate test case. — andreasg, Jul 26 '12 at 21:00
The broadcast receiver is actually working just fine. As I said at the bottom of the post above, calling context.sendBroadcast gets into onReceive. It's the service initialization that I don't see happening. — pbaumann, Jul 26 '12 at 21:37
did you find a solution? I'm facing the same problem trying to test an `IntentService` — Gal Ben-Haim, Aug 19 '12 at 08:22

score 12 · Accepted Answer · answered Oct 17 '12 at 12:42

You can't test the service initialization like you're trying to do. When you create a new activity under Robolectric, the activity you get back is actually a ShadowActivity (kind of). That means when you call startService, the method that actually gets executed is this one, which just calls into ShadowApplication#startService. This is the contents of that method:

@Implementation
@Override
public ComponentName startService(Intent intent) {
    startedServices.add(intent);
    return new ComponentName("some.service.package", "SomeServiceName-FIXME");
}

You'll notice that it doesn't actually try to start your service at all. It just notes that you attempted to start the service. This is useful for the case that some code under test should start the service.

If you want to test the actual service, I think you need to simulate the service lifecycle for the initialization bit. Something like this might work:

@RunWith(RobolectricTestRunner.class)
public class MyServiceTest{
    @Test
    public void testPurchaseHappyPath() throws Exception {

        Intent startIntent = new Intent(Robolectric.application, MyService.class);
        MyService service = new MyService();
        service.onCreate();
        service.onStartCommand(startIntent, 0, 42);

        // TODO: test test test

        service.onDestroy();
    }
}

I'm not familiar with how Robolectric treats BroadcastReceivers, so I left it out.

EDIT: It might make even more sense to do the service creation/destruction in JUnit @Before/@After methods, which would allow your test to only contain the onStartCommand and "test test test" bits.

Robolectric and IntentServices

1 Answers1