[PR #6139] [CLOSED] Fix flaky VerificationCodeScreenTest overflow menu test #120247

Closed
opened 2026-06-09 18:06:13 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/6139
Author: @SaintPatrck
Created: 11/7/2025
Status: Closed

Base: mainHead: fix-flaky-test


📝 Commits (2)

  • 5e61c1e Fix flaky VerificationCodeScreenTest overflow menu test
  • 19b5fad Fix flaky QrCodeScanScreenTest in landscape mode

📊 Changes

2 files changed (+4 additions, -3 deletions)

View changed files

📝 app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/qrcodescan/QrCodeScanScreenTest.kt (+2 -0)
📝 app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/verificationcode/VerificationCodeScreenTest.kt (+2 -3)

📄 Description

🎟️ Tracking

N/A

📔 Objective

Fix flaky VerificationCodeScreenTest > on overflow item click should display menu test that intermittently fails with FutureGarbageCollectedException in CI.

Root Cause: The test used .isDisplayed() matcher which returns immediately without waiting for Compose recomposition, creating a race condition with asynchronous popup rendering.

Solution: Replace .isDisplayed() with .assertIsDisplayed() to properly wait for the Compose UI to settle before verification. This aligns with the established pattern used in other menu interaction tests within the same file (lines 426-455).

Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/6139 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 11/7/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix-flaky-test` --- ### 📝 Commits (2) - [`5e61c1e`](https://github.com/bitwarden/android/commit/5e61c1e9897ff0d2fe3db0d744efe9200ec05038) Fix flaky VerificationCodeScreenTest overflow menu test - [`19b5fad`](https://github.com/bitwarden/android/commit/19b5fad0bbc70685a1818408202190bfb2e354e6) Fix flaky QrCodeScanScreenTest in landscape mode ### 📊 Changes **2 files changed** (+4 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/qrcodescan/QrCodeScanScreenTest.kt` (+2 -0) 📝 `app/src/test/kotlin/com/x8bit/bitwarden/ui/vault/feature/verificationcode/VerificationCodeScreenTest.kt` (+2 -3) </details> ### 📄 Description ## 🎟️ Tracking N/A ## 📔 Objective Fix flaky VerificationCodeScreenTest > on overflow item click should display menu test that intermittently fails with FutureGarbageCollectedException in CI. Root Cause: The test used .isDisplayed() matcher which returns immediately without waiting for Compose recomposition, creating a race condition with asynchronous popup rendering. Solution: Replace .isDisplayed() with .assertIsDisplayed() to properly wait for the Compose UI to settle before verification. This aligns with the established pattern used in other menu interaction tests within the same file (lines 426-455). ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-09 18:06:13 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#120247