Intermittent UI test failure - ThreeDotMenuTest.openSyncedTabsTest

Open
#1,654 7 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, kotlin
Domain
mobile, testing-qa

Research direction

Start by running ThreeDotMenuTest.openSyncedTabsTest and compare its behavior with the linked Firebase Test Run. Read SyncedTabsRobot.kt around assertNotSignedInSyncTabsView and ThreeDotMenuRobot.kt around openSyncedTabs, then trace the calls at ThreeDotMenuTest.kt lines 244-245. Done means the test reliably verifies the expected signed-out synced-tabs view.

Written by the indexing model from the issue text.

Description

eng:ui-test
Firebase Test Run:

https://console.firebase.google.com/project/moz-reference-browser-230023/testlab/histories/bh.b4e77beaed81bc1c/matrices/8064582217005320246/executions/bs.b28ffd41c1b8f3fc/testcases/1### Stacktrace:
junit.framework.AssertionFailedError at junit.framework.Assert.fail(Assert.java:48) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.mozilla.reference.browser.ui.robots.SyncedTabsRobot.assertNotSignedInSyncTabsView(SyncedTabsRobot.kt:31) at org.mozilla.reference.browser.ui.robots.SyncedTabsRobot.verifyNotSignedInSyncTabsView(SyncedTabsRobot.kt:21) at org.mozilla.reference.browser.ui.ThreeDotMenuTest$openSyncedTabsTest$5.invoke(ThreeDotMenuTest.kt:245) at org.mozilla.reference.browser.ui.ThreeDotMenuTest$openSyncedTabsTest$5.invoke(ThreeDotMenuTest.kt:244) at org.mozilla.reference.browser.ui.robots.ThreeDotMenuRobot$Transition.openSyncedTabs(ThreeDotMenuRobot.kt:121) at org.mozilla.reference.browser.ui.ThreeDotMenuTest.openSyncedTabsTest(ThreeDotMenuTest.kt:244)

Build:

Master 8/16 (AC update)

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla-mobile/reference-browser

All issues in mozilla-mobile/reference-browser

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.