Skip to content

test(goldens): cover Settings page BitBox-open variant#590

Merged
TaprootFreak merged 3 commits into
chore/post-580-followupsfrom
test/settings-golden-bitbox
May 26, 2026
Merged

test(goldens): cover Settings page BitBox-open variant#590
TaprootFreak merged 3 commits into
chore/post-580-followupsfrom
test/settings-golden-bitbox

Conversation

@TaprootFreak
Copy link
Copy Markdown
Contributor

Summary

  • Handbook (docs/handbook/de/index.html:1088-1090) behauptet, die Wallet-Sicherung-Kachel ist bei BitBox-Wallet ausgeblendet
  • Bestehender Golden deckt nur die Software-Wallet-Variante ab — Invertierung der Bedingung in settings_page.dart:100 würde nicht auffallen
  • Neuer goldenTest „bitbox wallet open hides the Wallet-Sicherung tile" sichert die hidden-tile-Logik ab
  • MockBitboxWallet in test/helper/golden_mocks.dart ergänzt (analog zu MockSoftwareWallet)

Schließt Reviewer-Finding #2 aus dem #582-Review.

Test plan

  • CI grün (Visual Regression, Analyze & Test, Coverage Floor Gate, Handbook Build Check)
  • Goldens via golden-regenerate.yaml auf dfx01 generiert (erwartet: 1 neuer PNG settings_page_bitbox.png)
  • Manuell verifiziert: PNG zeigt Settings-Page ohne Wallet-Sicherung-Tile

The Handbook claims the Wallet-Sicherung tile is hidden when a BitBox
wallet is open (settings_page.dart:100 gates it on
walletType == WalletType.software). The existing golden only covers
the software-wallet branch — invert the condition by mistake and no
test fails. Add a sibling goldenTest with a BitBox wallet so the
hidden-tile contract is locked in by a baseline.
@TaprootFreak TaprootFreak marked this pull request as ready for review May 26, 2026 15:38
@TaprootFreak TaprootFreak merged commit f2545e3 into chore/post-580-followups May 26, 2026
6 checks passed
@TaprootFreak TaprootFreak deleted the test/settings-golden-bitbox branch May 26, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant