Intermittent UI test failure - AddonsTest.removeAddonTest

Open
#1,710 11 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, kotlin
Domain
mobile, testing

Research direction

Start with removeAddonTest in AddonsTest.kt and follow the stack trace through ThreeDotMenuRobot.kt, AddonsManagerRobot.kt, and UiDevice.kt. Reproduce the Firebase-reported failure and inspect why waitAndInteract does not find the expected element. Done means the test no longer intermittently fails while removing an addon.

Written by the indexing model from the issue text.

Description

eng:intermittent-test eng:ui-test
Firebase Test Run:

Flaky 1/2 tries.
https://console.firebase.google.com/project/moz-reference-browser-230023/testlab/histories/bh.b4e77beaed81bc1c/matrices/7623436030602708407/executions/bs.e0c7fc91709e535c

Stacktrace:

java.lang.AssertionError at org.junit.Assert.fail(Assert.java:87) at org.junit.Assert.assertTrue(Assert.java:42) at org.junit.Assert.assertNotNull(Assert.java:713) at org.junit.Assert.assertNotNull(Assert.java:723) at org.mozilla.reference.browser.ext.UiDeviceKt.waitAndInteract(UiDevice.kt:20) at org.mozilla.reference.browser.ui.robots.AddonsManagerRobot.dismissAddonDownloadCompletedPrompt(AddonsManagerRobot.kt:60) at org.mozilla.reference.browser.ui.AddonsTest$removeAddonTest$3.invoke(AddonsTest.kt:98) at org.mozilla.reference.browser.ui.AddonsTest$removeAddonTest$3.invoke(AddonsTest.kt:93) at org.mozilla.reference.browser.ui.robots.ThreeDotMenuRobot$Transition.openAddonsManager(ThreeDotMenuRobot.kt:136) at org.mozilla.reference.browser.ui.AddonsTest.removeAddonTest(AddonsTest.kt:93)

Build:

debug 11/4. Started with #1704

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.