android / android/testing-samples

Robolectric 4 support

Abierto
#237 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Java
Estrellas
9.3k
Forks
3.6k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

As I have read, tests written with androidx.test.* are supposed to be executed either as an instrumented test (in a real device or emulator) or in the JVM with robolectric 4. So I have copied the ChangeTextBehaviorKtTest in the test folder, and I have added robolectric 4 dependency to gradle file. Also I have copied the rest of androidx.test.* dependencies with testImplementation keyword. Everything seems ok, until I try to execute the tests.

This is what I get:

[Robolectric] com.example.android.testing.espresso.BasicSample.ChangeTextBehaviorKtTest2.changeText_sameActivity: sdk=28; resources=binary
Called loadFromPath(/system/framework/framework-res.apk, true); mode=binary sdk=28

androidx.test.espresso.PerformException: Error performing 'close keyboard' on view 'with id: com.example.android.testing.espresso.BasicSample:id/editTextUserInput'.

Caused by: java.lang.RuntimeException: Attempt to close the soft keyboard did not result in soft keyboard to be hidden. resultCode = -1

So I have removed the call to closeSoftKeyboard() function, as I have noticed that is not necessary with instrumented tests so that they can be executed successfully.

When I remove the call to that funcion, the first test changeText_sameActivity is executed successfully, but the second still fails, with this new exception:

[Robolectric] com.example.android.testing.espresso.BasicSample.ChangeTextBehaviorKtTest2.changeText_newActivity: sdk=28; resources=binary
Called loadFromPath(/system/framework/framework-res.apk, true); mode=binary sdk=28

androidx.test.espresso.NoMatchingViewException: No views in hierarchy found matching: with id: com.example.android.testing.espresso.BasicSample:id/show_text_view

View Hierarchy:
+>DecorView{id=-1, visibility=VISIBLE, width=320, height=470, has-focus=true, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, layout-params={(0,0)(fillxfill) ty=APPLICATION wanim=0x10302f8
fl=LAYOUT_IN_SCREEN LAYOUT_INSET_DECOR SPLIT_TOUCH HARDWARE_ACCELERATED DRAWS_SYSTEM_BAR_BACKGROUNDS
pfl=FORCE_DRAW_STATUS_BAR_BACKGROUND}, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1}

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza con el ChangeTextBehaviorKtTest copiado y las dependencias de prueba de Gradle descritas en la issue, y luego ejecuta changeText_sameActivity y changeText_newActivity bajo Robolectric 4. Compara el fallo del teclado y la jerarquía show_text_view ausente con el comportamiento instrumentado; se considera terminado cuando ambas pruebas se ejecutan correctamente sin eliminar la acción del teclado.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Área
testing
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.