android / android/android-test
Flaky Espresso.intended() won't find anything sometimes
- Vorherrschende Sprache
- Java
- Sterne
- 1.2k
- Forks
- 342
- Ø Merge
- 11 Std. 29 Min.
- Gemergte PRs (30 T.)
- 2
Beschreibung
Description
Flaky Espresso.intended() won't find anything sometimes.
Steps to Reproduce
Run the test **proveEspressoIntendedIssue0** (ignore other tests in there!) here: https://github.com/mobilekosmos/EspressoDialogsIssue/blob/master/app/src/androidTest/java/com/issues/espressoidling/MainActivity2Test.kt
The issue doesn't only happen because of using the loop, this is also happening when running the test manually, but difficult to reproduce when doing so, it works a few times, then it doesn't, therefore the loop where it was always reproducible till now on a Pixel 3a.
Expected Results
Espresso.intended() shuould always find a view.
Actual Results
Sometimes Espresso.intended() will hang and not find anything.
AndroidX Test and Android OS Versions
Android R Preview 4
androidTestImplementation 'androidx.test.ext:junit:1.1.1'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'
implementation 'androidx.test.espresso:espresso-idling-resource:3.2.0'
androidTestImplementation("androidx.test.espresso:espresso-intents:3.2.0")
Link to a public git repo demonstrating the problem:
https://github.com/mobilekosmos/EspressoDialogsIssue/blob/master/app/src/androidTest/java/com/issues/espressoidling/MainActivity2Test.kt
p.s.: could you please stop closing issues so fast without really taking a good look into it? It's the third time I must open this issue because you didn't look at the pointed location.
Beitragsleitfaden
Rechercherichtung
Beginne mit app/src/androidTest/java/com/issues/espressoidling/MainActivity2Test.kt und führe nur proveEspressoIntendedIssue0 mit den aufgeführten AndroidX Test- und Espresso-Versionen aus. Reproduziere das sporadische Hängen auf Android R Preview 4 und ermittle anschließend, warum Espresso.intended() die View manchmal nicht findet. Als erledigt gilt die Aufgabe, wenn der Test die beabsichtigte View zuverlässig findet.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- android, kotlin
- Bereich
- mobile, testing
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 30/100