Eshwari007

Results 17 issues of Eshwari007

The user is testing version v3.2.0 - An user signs in with a secret key - Upon receiving the password screen, the user realized that it was a wrong account...

Bug ๐Ÿ›
security
๐Ÿ›ฌ Onboarding

For example, when sending a tx and then using the Send max functionality, the outbound pending tx isn't considered. The above issue has been fixed for STX https://github.com/hirosystems/stacks-wallet-web/issues/1701 This ticket...

Enhancement ๐Ÿ’ก

Use case scenario: - The user sends `Max `STX token to another account - Tx is now pending - The user selects the send button again - The user still...

Enhancement ๐Ÿ’ก

https://btc-website.tintashlabs.com/get/testhiro.btc While testing PR:#1827 User tried to delete the BNS name onto an existing account User received pop up dialogue that it has been submitted however,user does not see the...

Bug ๐Ÿ›
P2 Bug ๐Ÿ•ท
bns

The issue above was derived from wallet channel 1) Do you know why Hiro web wallet extension on Firefox takes such a long time to load the wallet? Much longer...

๐ŸŽ Performance

While testing the web wallet with a basic tx transfer between two accounts, noticed that the view_transaction_signing was triggered several times on Sentry. It's triggered multiple times because the app...

bug
bug-p3
needs:metrics

Bug found testing Stacks Wallet build e4f41fb, 4.2.0. Environment:Test Net Actual scenario: This is a minor issue but felt can be an issue if the user is moving their mouse...

P4 Bug ๐Ÿœ
reported-from-ui
Visual bug ๐Ÿงผ

The objective below was provided by @andresgalante to outline the start of API automation for the below. The goal is to bring test coverage up to 80% in these scenarios:...

tests

Environment:TestNet URL:https://explorer-git-feat-microblocks-final-blockstack.vercel.app/sandbox/contract-call Seems like the middle section in sandbox-explorer is truncated and is not able to navigate from left to right as there is no scroll from left to right.There...

Bug ๐Ÿ›
P4 Bug ๐Ÿœ
sandbox

The issue will be revisited after Explorer's refactor as currently, all errors will be 404 or 500s which is the default error page for nextjs. This bug will be retested...

Enhancement ๐Ÿ’ก