test(suite): reorganize manual release tests to match the new SW team structure - #32193
Open
honzauher wants to merge 1 commit into
Open
test(suite): reorganize manual release tests to match the new SW team structure#32193honzauher wants to merge 1 commit into
honzauher wants to merge 1 commit into
Conversation
⚡️ Performance report (alpha)Note Alpha release: The limits are still being calibrated, and each measurement is desktop / group 4🟢 Within limits.Each metric reads
desktop / group 3🟢 Within limits.Each metric reads
|
honzauher
force-pushed
the
manual-release-tests-redistribution
branch
from
September 8, 2026 11:31
2a72f40 to
c87491e
Compare
honzauher
force-pushed
the
manual-release-tests-redistribution
branch
from
September 8, 2026 13:49
c87491e to
8b2c9cf
Compare
Ondra-Zik
reviewed
Sep 8, 2026
Contributor
There was a problem hiding this comment.
I will change my test cases when needed drop this please
Ondra-Zik
reviewed
Sep 8, 2026
Contributor
There was a problem hiding this comment.
same here I will change my test cases when needed drop this please
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Follow-up on manual release tests after #31987 landed. That PR already assigned a
stream to every test and made it mandatory via typing and lint, so the stream
reassignment this PR originally carried is gone — everything here is what #31987
did not cover. Rebased on develop; 26 files.
Manual steps brought up to date — the app had moved on and the steps no longer
matched it:
detail modal, and "Cancel transaction" sits next to it.
not two tick boxes.
is desktop-only.
remember-walletrewritten for the eject model — the "remember wallet" switch isgone, wallets persist by default and are ejected.
check-updateandapplication-resetassertions widened to what the codeactually does (button states, autostart, IndexedDB, remembered wallets).
metadata/labelshad "Define me please." as its only step; now covers the SuiteSync labelling flows on Windows/macOS, where the automated suite does not run.
Deleted
btc/btc-transactions— duplicatedaccount/transactions"Speed up and cancel apending transaction"; its one unique step (pending tx visible in both accounts)
was moved there.
dashboard/portfolio— subset ofdashboard-wallet"Portfolio graph".settings/wallet-loading— the "Wallet loading" section no longer exists inSettings/Device.
Added — six tests for areas with no coverage at all, manual or automated:
account/named-address— ENS resolutionconnect/bluetooth-pairing— Bluetooth/THP lifecyclesettings/pin-and-wipe-codesettings/safety-checks— Strict vs Promptsettings/bio-auth— Touch ID / Windows Hellosettings/forget-device— all five flow branchesOther
MacOSInteldropped from everyosMatrixexceptauto-update, where the Macarchitecture genuinely matters for install and code signing.
per the scope doc's "Coinjoin acc." ownership.
Network: message signing, custombackend/explorer, Tron energy, Stellar token activation, coin-specific send.
Notes for QA
Three of the new tests need a look before they go into the release round:
pin-and-wipe-code— the second case erases the device, since that is theonly way to verify a wipe code. Needs a disposable seed and a deliberate
decision about including it.
safety-checks— the second case does not yet name a concrete action that Strictrefuses and Prompt allows. Written generically; please fill it in.
metadata/labels— the previous steps were a placeholder, so the new ones are myreading of the note that the coverage is automated on Linux only. Please
sanity-check them against what actually needs re-running off Linux.
account/named-addresscovers Suite only. Develop now also resolves ENS names inthe suite-native send form, so the same gap exists on mobile and is not addressed
here.
Related Issue
Resolve
Screenshots:
🌐 Preview deployments
🌐 Suite Web preview: https://dev.suite.sldev.cz/suite-web/manual-release-tests-redistribution/web/
🔍 Currents Test Results
🔍 Suite desktop test results: View in Currents
🔍 Suite web test results: View in Currents
🔒 Quarantined E2E Tests
Trezor Suite (web) — 3 test(s)
Updated: 2026-09-08T13:55:12.777Z • 3 test(s) total
Trezor Suite (desktop) — 5 test(s)
Updated: 2026-09-08T13:54:45.392Z • 5 test(s) total