@Eugen Martynov I agree in that case that mvp lib doesn't fit, but the idea behind it does. Keep the service behind an interface for all android related features, and keep logic in separate class, it's easy to mock an interface, but not so easy android classes... But if you really don't think it's worth separating, than maybe try robolectic....