Espresso - withEffectiveVisibility vs isDisplayed

unit-testing testing junit4 android-espresso
Daniel Gomez Rico picture Daniel Gomez Rico · Jul 6, 2015 · Viewed 7.5k times · Source

Whats´s the difference between isDisplayed and withEffectiveVisibility?

onView(withText("Much Dagger")).check(matches(withEffectiveVisibility(ViewMatchers.Visibility.VISIBLE)));


onView(withText("Much Dagger")).check(matches(ViewMatchers.isDisplayed());

Answer

UDI picture UDI · Jul 20, 2015

According to the Documentation

Returns a matcher that matches {@link View}s that have "effective" visibility set to the given value. Effective visibility takes into account not only the view's visibility value, but also that of its ancestors. In case of View.VISIBLE, this means that the view and all of its ancestors have visibility=VISIBLE. In case of GONE and INVISIBLE, it's the opposite - any GONE or INVISIBLE parent will make all of its children have their effective visibility.

Note:

Contrary to what the name may imply, view visibility does not directly translate into whether the view is displayed on screen (use isDisplayed() for that). For example, the view and all of its ancestors can have visibility=VISIBLE, but the view may need to be scrolled to in order to be actually visible to the user. Unless you're specifically targeting the visibility value with your test, use isDisplayed.

So if using for verifying if a view is visible use isDisplayed() but for other verification incase if invisible and gone use withEffectiveVisibilty()

Related questions

Cleanup after all junit tests

In my project I have to do some repository setup before all tests. This is done using some tricky static rules. However I've got no clue how to do clean up after all the tests. I don't want to keep …

Read More
Junit: splitting integration test and Unit tests

I've inherited a load of Junit test, but these tests (apart from most not working) are a mixture of actual unit test and integration tests (requiring external systems, db etc). So I'm trying to think of a way to actually …

Read More
Test expected exceptions in Kotlin

In Java, the programmer can specify expected exceptions for JUnit test cases like this: @Test(expected = ArithmeticException.class) public void omg() { int blackHole = 1 / 0; } How would I do this in Kotlin? I have tried two syntax variations, but none of them …

Read More