You have probably heard already a tremendous number of times that unit-testing your Android code is important. It’s all true and still valid. And there is one recipe I tend to forget quite often, which I also found extremely useful, while writing tests exercising (or relying onto) any external data.
In this scenario, all the content is kept outside of the unit-test itself and is simply read at runtime from resources (aka assets).
Read more →