Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual test run on Linux for Ethereum Remote Client 1.0.12 #6681

Closed
17 tasks done
kjozwiak opened this issue Oct 31, 2019 · 2 comments
Closed
17 tasks done

Manual test run on Linux for Ethereum Remote Client 1.0.12 #6681

kjozwiak opened this issue Oct 31, 2019 · 2 comments

Comments

@kjozwiak
Copy link
Member

kjozwiak commented Oct 31, 2019

Per release specialty tests

  • Infura interactions should be behind fastly proxy cache.(#6614)

Branding

  • Verify there are no appearances of the word MetaMask
  • Verify links to MetaMask resources such as websites and email should point to Brave resources
  • Verify all downloadable resources (Seed/Logs) contains Brave file names
  • Verify MetaFox logo is not present on any screen

Component

  • Verify Ethereum client component is downloaded when you open brave://wallet for the first time
  • Verify Ethereum client component is successfully updated and doesn't corrupt the browser wallet
  • Delete component folder. Verify the component is downloaded successfully after browser relaunch

Ðapps

  • Verify Ðapp can successfully connect to your crypto wallets account, signed via a pop-up notification
  • Verify Ðapp transactions where assets are set/received show up in the account activity view within the extension

Import & Recovery

  • Verify you can import Brave Crypto Wallet using 24 seed words
  • Verify you can import MetaMask Wallet using only 12 seed words

Transactions

  • Verify Eth/ERC-20 tokens can be received at the addresses generated for your account
  • Verify Eth/ERC-20 tokens can be sent to other addresses from your account
  • Verify a successful transaction can be done on a restored wallet

Hardware

  • Verify you can link hardware wallet using Trezor and unlock the wallet
  • Verify you can link hardware wallet using Ledger Nano and unlock the wallet
@kjozwiak
Copy link
Member Author

The Component section can be checked once we push the new extension out. Because we're loading the extension using the Load Unpacked method, it's difficult to QA the component section without the new extension being live.

@srirambv
Copy link
Contributor

srirambv commented Nov 1, 2019

Looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants