INVISIBLE: The view is invisible, but it still takes up space for layout purposes

VISIBLE: The view is rendered as something that should be visible There are two other possible values: INVISIBLEand GONE. If you look at the list on the right side in image one, you’ll see getVisibility() listed with value VISIBLE. The withEffectiveVisibility() matcher checks how the visibility of a view is set in the code. If a view exists in the hierarchy that’s no guarantee that it’s also visible. “made_up_view_id” does not exist in the hierarchy: onView(withId(R.id.made_up_view_id)).check(doesNotExist())Īnd onView(withId(R.id.list_item_icon)).check(doesNotExist()) would fail, because that id exists in the current hierarchy. Instance the following example will pass, because the view with id The doesNotExist() viewĪssertion checks if a view exists in the current view hierarchy. The one that’s selected is an ImageView, below that there’s a On the left side you can see a hierarchy of the views that are used Take for example this language translation app: Image 1. I will discusses all three options and how they relate to each other, starting off with doesNotExist().Ĭhances are that the UI of the app that you’re checking contains multiple views. Choosing the right matcher to check your view One that works for your scenario under all circumstances and on all That’s why it’s important to pick the right Matchers are related, but check different aspects that play a role in (this last one is actually a view assertion, not a matcher). Espresso supplies a few matchers that might be useful: Sometimes you’ll want to check whether a view is displayed or not during a test.

Android testview set visible