kWallet / signing — QA status

Only the wallet and signing tests, only their current state. For history — when something started failing — use the retest grid. What each test actually does: the test index (ids below are T:-prefixed and link there — bare capitals mean a task, not a test). Scenario definitions: every WalletConnect path. QA home

loading…

What automation cannot cover

Signing with the wallet backgrounded on a phone. kWallet is always awake, so it can never fail this — a green here would mean nothing. Needs a real device.
A deliberately slow approval (sit on it ~45s). Guards a timeout cap that was wrong once already.
HashPack's own session lifecycle — clearing connections by hand, extension vs mobile app.
Animation and timing judgement — whether the wiper/confetti lands at the right moment.