Up until now, Robolectric has relied on rough approximations of...
Up until now, Robolectric has relied on rough approximations of the Android framework’s resource handling logic, backwards-engineered to be ‘good enough’ for many testing purposes.
Your Robolectric maintainers are pleased to announce the release of Robolectric 3.3! There’s been a bunch of activity recently in Robolectric, and we wanted to give a quick update on our thinking about where the project is going.
Robolectric needs access to multiple Android SDK jars in order to perform its magic, which means it needs special configuration beyond just setting up dependencies in your build. By default, it tries to download Android SDK jars from Maven Central.