Intermittent UI test failure - <ReaderViewTest.verifyReaderViewDetectionTest>
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- mobile, testing-qa
Research direction
Start with the Firebase Test Run and the failure in ReaderViewTest.kt:49, then inspect ReaderViewRobot.kt:183 and NavigationToolbarRobot.kt:81 around SessionLoadedIdlingResource. Run verifyReaderViewDetectionTest and compare successful and timed-out executions. Done means the test completes reliably without the IdlingResourceTimeoutException.
Written by the indexing model from the issue text.
Description
Firebase Test Run: Firebase link
Stacktrace:
androidx.test.espresso.IdlingResourceTimeoutException: Wait for [SessionLoadedIdlingResource] to become idle timed out
at dalvik.system.VMStack.getThreadStackTrace(Native Method)
at java.lang.Thread.getStackTrace(Thread.java:1720)
at androidx.test.espresso.base.DefaultFailureHandler.getUserFriendlyError(DefaultFailureHandler.java:88)
at androidx.test.espresso.base.DefaultFailureHandler.handle(DefaultFailureHandler.java:51)
at androidx.test.espresso.ViewInteraction.waitForAndHandleInteractionResults(ViewInteraction.java:312)
at androidx.test.espresso.ViewInteraction.check(ViewInteraction.java:297)
at org.mozilla.fenix.ui.robots.ReaderViewRobotKt.assertAppearanceButtonDoesntExists(ReaderViewRobot.kt:183)
at org.mozilla.fenix.ui.robots.ReaderViewRobotKt.access$assertAppearanceButtonDoesntExists(ReaderViewRobot.kt:1)
at org.mozilla.fenix.ui.robots.ReaderViewRobot.verifyAppearanceButtonDoesntExists(ReaderViewRobot.kt:34)
at org.mozilla.reference.browser.ui.ReaderViewTest$verifyReaderViewDetectionTest$7.invoke(ReaderViewTest.kt:49)
at org.mozilla.reference.browser.ui.ReaderViewTest$verifyReaderViewDetectionTest$7.invoke(ReaderViewTest.kt:48)
at org.mozilla.reference.browser.ui.robots.NavigationToolbarRobot$Transition.clickReaderViewButton(NavigationToolbarRobot.kt:81)
at org.mozilla.reference.browser.ui.ReaderViewTest.verifyReaderViewDetectionTest(ReaderViewTest.kt:48)
at java.lang.reflect.Method.invoke(Native Method)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at androidx.test.internal.runner.junit4.statement.RunBefores.evaluate(RunBefores.java:80)
at androidx.test.internal.runner.junit4.statement.RunAfters.evaluate(RunAfters.java:61)
at androidx.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:527)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56)
at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:388)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2189)
Build: 8/15 Main
- Dominant language
- Kotlin
- Stars
- 668
- Forks
- 198
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 53
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mozilla-mobile/reference-browser
-
🐞 bug
Difficulty 1/5 Under an hour Newbie friendliness 55/100
mozilla-mobile/reference-browser#4174 ·
Maintainers usually reply within 1 day
-
🐞 bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
mozilla-mobile/reference-browser#4072 ·
Maintainers usually reply within 1 day
-
Snackbars have wrong anchoring / paddingMay be free again A pull request for this issue was closed without being merged. Open🐞 bug
Difficulty 3/5 1-2 days Newbie friendliness 42/100
mozilla-mobile/reference-browser#3746 · 1 comment ·
Maintainers usually reply within 1 day
-
🐞 bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mozilla-mobile/reference-browser#3083 · 1 comment ·
Maintainers usually reply within 1 day
-
🐞 bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mozilla-mobile/reference-browser#2538 ·
Maintainers usually reply within 1 day
All issues in mozilla-mobile/reference-browser
Similar issues
-
Bug Domain changed
Difficulty 1/5 Under an hour Newbie friendliness 79/100
keiyoushi/extensions-source#21174 ·
Maintainers usually reply within 1 day
-
Unified account interface not translated into Simplified ChinesePossibly taken @xuenhua claimed this 3 days ago. Openunconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
thunderbird/thunderbird-android#11936 · 1 comment ·
Maintainers usually reply within 3 days
-
Update toast stylingOpendesign good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
scribe-org/Scribe-Android#778 ·
Maintainers usually reply within 1 day
-
Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ankidroid/Anki-Android#23392 ·
Maintainers usually reply within 1 day
-
AI Generated CI/CD ⚒️ Flaky-tests 🐦 go 🏃
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
valkey-io/valkey-glide#7772 ·
Maintainers usually reply within 1 day