Verifying Fragments With Espresso

I’ve done some searching to see how I can use Espresso to validate the navigation throughout my app. My typical set-up is one activity encompassing whichever fragments make sense to be managed by that activity (adding additional activities with their own fragments as necessary). In my searching, however, all I was finding were people suggesting I select a View that is displayed within that fragment, and check for its existence.

But that seems a little too fragile to me, layouts can change fairly easily as projects progress and so I figured, since there seems to be no way to actually check that the fragment itself is displayed, just give the master layout an id and look for that instead.  I see less chance for that to change than I do a view within it.

It’s such a minuscule alteration but I think, how it’s performed currently, this is less likely to fail throughout an app’s evolution.

And if that hasn’t convinced you here’s a picture — 9000 seconds in Paint.

layout-2016-02-04-164407

error: ‘;’ expected

I just had a frustrating configuration hunt. I was creating an Espresso test-file for a new app I’m making, and after writing just the tiniest bit of boilerplate I wanted to verify¬†everything was working properly, ran the Gradle connectedAndroidTest configuration and got the below…

error: type annotations are not supported in -source 1.7
(use -source 8 or higher to enable type annotations)

Continue Reading →