metamask-mobile
metamask-mobile copied to clipboard
feat: v7.22.0
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.
Testing iOS v.7.22.0 (1321)
Onboarding: custom ETH mainnet ✅ Custom mainnet Scenario 1 (Verifying Custom Mainnet Screen Appears): ✅ Custom mainnet Scenario 2 (Entering an Invalid Mainnet RPC URL): ✅ Custom mainnet Scenario 3 (Entering a valid mainnet RPC URL): ✅ Custom mainnet Scenario 4 (Editing a custom mainnet URL on the settings and privacy view): ✅ Custom mainnet Scenario 5 (Deleting a custom mainnet URL on the settings and privacy view): https://drive.google.com/file/d/1mLsAHvieYRVfKMak8X7znU0nGBV9gnUR/view
QR Scanner Regression ✅ From the in-app camera I should be able to scan a valid QR code containing an address: ✅ I should be able to use the QR scanner on the send flow to scan an address: https://drive.google.com/file/d/11VVW89DBWRKJexv0Q-6zhGVsEfgQXTEB/view
✅ When I scan a dapp QR code using the in-app camera I should see the appropriate warning message: ✅ When I scan a dapp QR code using the QR scanner on the send flow I should see the appropriate error message: https://drive.google.com/file/d/1mLsAHvieYRVfKMak8X7znU0nGBV9gnUR/view?usp=sharing
❌ When I scan an invalid address QR code using the in app camera I should see the appropriate warning message:
❗Scanning invalid QR from the in-app camera produces Invalid deeplink
errors
✅ When I scan an invalid address QR code using the QR scanner on the send flow I should see the appropriate warning message: https://drive.google.com/file/d/10FF_6BQd5PH4O6wRFVbX-A8v2_uUL1sk/view
❌ A user can scan a private key QR code using the in-app camera to import an account:
❗Import is successful but throws Invalid deeplink/URL
error followed by the account’s private key string
https://drive.google.com/file/d/1InA1_wPjODUwxrjqOrSER1l-3gR8e0hM/view
❌ User scans MMM Receive QR code on different network: ❗”Network with chain id 0x1 not found your wallet” error when scanning Eth receive QR from another network https://drive.google.com/file/d/1OjK34MsogEyVUIXOrC_UEkkABGe_pOtC/view
General view ✅ Scenario: Changing the device language from English to Russian: ❗Your Wallet is Ready open modal is in English https://drive.google.com/file/d/1VREQs_EKOzc_LdPswj6_v4kM9rkzsqcT/view
✅ Scenario: Changing the app language from English to Filipino: https://drive.google.com/file/d/1Xwi2Gxe9eRbi8go7jpCcheKwgs8HlgX_/view
Browser Regression ✅ Scenario: Searching an invalid url and prompts the user with an error message: ✅ Scenario: Navigation with browser controls: ✅ Scenario: ENS website loads correctly: ✅ Scenario: From the browser I can successfully upload a picture: ✅ Scenario: Address bar: https://drive.google.com/file/d/1LxdVWjDmL2oyX6MvpSIf24uz6JRt_rcV/view
✅ Scenario: Adding browser Favorites: ✅ Scenario: Browser Options Menu: ✅ Scenario: Visiting a malicious website prompts the user with the phishing detection warning: ✅ Scenario: Navigate to DappsMarketplace and connect wallet account: https://drive.google.com/file/d/1srvanDsg35pgP0uMaNy6bp5XdTX3gwQ8/view
Network Regression ✅ Scenario: I can remove a custom network (Palm) that was added via the popular network flow: ✅ Scenario: I can remove a custom network that was added via the custom network flow. ✅ Scenario Outline: Adding a network via a Dapp: ✅ Scenario Adding a network via the new popular network flow: ✅ Scenario: Adding a network via the custom network flow: ✅ Scenario: Adding a custom network and editing the network: ✅ Scenario: Editing a popular network: https://drive.google.com/file/d/17XiQbaIzTpcCkkyryXR_q5hUl9sXMwo7/view
Testing Android v.7.22.0
Onboarding: custom ETH mainnet ✅ Custom mainnet Scenario 1 (Verifying Custom Mainnet Screen Appears): ✅ Custom mainnet Scenario 2 (Entering an Invalid Mainnet RPC URL): ✅ Custom mainnet Scenario 3 (Entering a valid mainnet RPC URL): ✅ Custom mainnet Scenario 4 (Editing a custom mainnet URL on the settings and privacy view): ✅ Custom mainnet Scenario 5 (Deleting a custom mainnet URL on the settings and privacy view): https://drive.google.com/file/d/1tLWIEg5-bb0CIlOaPBgUSc9djkQKIp7U/view?usp=drive_link
QR Scanner Regression ✅ From the in-app camera I should be able to scan a valid QR code containing an address: https://drive.google.com/file/d/1sFLQ5wf1Opn3K5wH9MFfgJErhu2pMXh4/view?usp=drive_link
✅ I should be able to use the QR scanner on the send flow to scan an address: https://drive.google.com/file/d/1sEAl_kfhQ08bGt8_OpGXEma-LJFSgSut/view?usp=drive_link
✅ When I scan a dapp QR code using the in-app camera I should see the appropriate warning message: https://drive.google.com/file/d/1s8qPIrkPeuvMuNSratEibzcXEZ-7NftO/view?usp=drive_link
✅ When I scan a dapp QR code using the QR scanner on the send flow I should see the appropriate error message: https://drive.google.com/file/d/1s7M_aP34wFysYPBLSqVFrWVHNeQlqgIm/view?usp=drive_link
✅ When I scan an invalid address QR code using the in app camera I should see the appropriate warning message: https://drive.google.com/file/d/1s5oi0C4_hJuMuxADrKhuaKIlpkKW11ou/view?usp=drive_link
✅ When I scan an invalid address QR code using the QR scanner on the send flow I should see the appropriate warning message: https://drive.google.com/file/d/1s2kHbUhwo4fMCLnfq1q1FXrLBox25jHg/view?usp=drive_link
❌ A user can scan a private key QR code using the in-app camera to import an account: ❗Import is successful but throws Invalid deeplink/URL error followed by the account’s private key string https://drive.google.com/file/d/1s1WqTSVcB4ybqu0oHaHvrc3BuFBduIqa/view?usp=drive_link
❌ User scans MMM Receive QR code on different network: ❗”Network with chain id 137 not found your wallet” error when scanning Eth receive QR from another network https://drive.google.com/file/d/1rynAy6t3WhWe4JM3QPlucwmG6F_Nmbbe/view?usp=drive_link
General view ✅ Scenario: Changing the device language from English to Russian: https://drive.google.com/file/d/1rrSNw5-CiW1oO7L0n5TmCCbA4pfz6Kx_/view?usp=drive_link
✅ Scenario: Changing the app language from English to Filipino: https://drive.google.com/file/d/1rqk7JKlOO3OhDSe3DqXNIy4IZXnV6OLe/view?usp=drive_link
Browser Regression ✅ Scenario: Searching an invalid url and prompts the user with an error message: https://drive.google.com/file/d/1sxslh6zOAOrVn1po4NRCgxWGM6MSopMy/view?usp=drive_link
✅ Scenario: Navigation with browser controls: https://drive.google.com/file/d/1swjlum7TOmq4B96IiEMj4Ew3DDsl6PuS/view?usp=drive_link
✅ Scenario: ENS website loads correctly: https://drive.google.com/file/d/1suk51TuJaS2JhTzjYQPvMObQMeCz1COg/view?usp=drive_link
✅ Scenario: From the browser I can successfully upload a picture: https://drive.google.com/file/d/1stDeCLFeicCoYgCGkA4es2aufGsBJGJa/view?usp=drive_link
✅ Scenario: Address bar: https://drive.google.com/file/d/1sm3O_YEmV0I-AkgRUVrJQmdTXZ6OrV3L/view?usp=drive_link
✅ Scenario: Adding browser Favorites: https://drive.google.com/file/d/1si_rva05JaRL2OYY9luUGpFvvhX0JDQt/view?usp=drive_link
✅ Scenario: Browser Options Menu: https://drive.google.com/file/d/1saAtYu6WiGhO9EI92bsdtPc_8mV7OoGY/view?usp=drive_link
✅ Scenario: Visiting a malicious website prompts the user with the phishing detection warning: https://drive.google.com/file/d/1sVpvsiOlRcT6mK964KJpBo0k9RxSyT7S/view?usp=drive_link
✅ Scenario: Navigate to DappsMarketplace and connect wallet account: https://drive.google.com/file/d/1sP4sTmE7S6xnmcGydecN82fqLqJTVgbG/view?usp=drive_link
Network Regression ✅ Scenario: I can remove a custom network that was added via the popular network flow: https://drive.google.com/file/d/1tHZlvT5d8LrrHW--cg2beqCxlmtckY83/view?usp=drive_link
✅ Scenario: I can remove a custom network that was added via the custom network flow: https://drive.google.com/file/d/1tDWOIYaXkz0moQQJELjqdQCEaPqoAyQm/view?usp=drive_link
✅ Scenario Outline: Adding a network via a Dapp: https://drive.google.com/file/d/1tCW6emuEYGP6uTjhPAGlUWfEHlsUY7a0/view?usp=drive_link
✅ Scenario Adding a network via the new popular network flow: https://drive.google.com/file/d/1t7stiqxJETffJus0YmZEAjt3S6S56ThX/view?usp=drive_link
✅ Scenario: Adding a network via the custom network flow: https://drive.google.com/file/d/1t7WBrRpRFRQZw733aua-JX6r8dJfC_Ic/view?usp=drive_link
✅ Scenario: Adding a custom network and editing the network: https://drive.google.com/file/d/1t0Cs-VqpAWqmc50oVpoFY9hFDzR8Jlq8/view?usp=drive_link
✅ Scenario: Editing a popular network: https://drive.google.com/file/d/1sz_QT76W5rrTmqs1Muy_jhOaJmTY0CSl/view?usp=drive_link
🟢 Approval from Accounts team
QA Sign-off for v7.22.0 build 1325
Bitrise
✅✅✅ pr_smoke_e2e_pipeline
passed on Bitrise! ✅✅✅
Commit hash: 103d49e7df5155b09c1746874f7ca2dbf5ba617e Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ca06f819-cab1-44e9-a035-d2507fe258e7
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipeline
on Bitrise by removing and re-applying theRun Smoke E2E
label on the pull request
Quality Gate passed
Issues
1 New issue
0 Accepted issues
Measures
0 Security Hotspots
87.0% Coverage on New Code
0.0% Duplication on New Code
Bitrise
✅✅✅ pr_smoke_e2e_pipeline
passed on Bitrise! ✅✅✅
Commit hash: 09abf8c0cf454c5c1636fe14e63adb5b3d116b6b Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/59088bb7-d1d8-4d3d-befb-9d0156dce7e5
[!NOTE]
- You can kick off another
pr_smoke_e2e_pipeline
on Bitrise by removing and re-applying theRun Smoke E2E
label on the pull request