UI tests are flaky about watchlater HOT 7 CLOSED

java.lang.RuntimeException: retrofit.converter.ConversionException: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.lambdasoup.watchlater.AddActivity$ErrorHandlingCallback.failure(AddActivity.java:409)

from watchlater.

android.support.test.espresso.NoMatchingViewException: No views in hierarchy found matching: with string from resource id: <2130968578>[choose_account] value: Choose account

from watchlater.

So far, none of those issues has reoccured. Close for the time being.

from watchlater.

All these issues still occur and are related:

• the NullPointerException in translateError is caused by the test already having finished, so the MockWebServer has already its responses cleared and emits a 404.
• the "target view should be visible but is not" failures are due to Espresso thinking that the activity has quietend
• there is a time interval between the first and the second http request that happen in the sometimes failing cases (authFail, addSuccess, addAlreadyInPlaylist) during which the retrofit http executor says it's idle, and apparently Espresso detects no activity on the main thread either. Hence, it tests its assertions, fails and possibly drags some related issues with it.

from watchlater.

Turning off animations on the test device (as recommended) is helpful, but not sufficient.

from watchlater.

Maybe updating to retrofit2 will help, because under the hood it uses AsyncTask.

from watchlater.

UI tests will be redone with moving to GAAC

from watchlater.