metamask-mobile
metamask-mobile copied to clipboard
feat: v7.23.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.
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
No data about Duplication
Testing iOS v.7.23.0 (1330)
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/1oowqJddZYzcXASpAgdXB6yDumX0baKe6/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/1SAZWppsaHUsJhzoY68SbZCCQfifwFR0z/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/1TMw-fSjHbfyy6pKHyHd8OeTpUqh0Zepf/view
✅ When I scan an invalid address QR code using the in app camera I should see the appropriate warning message: ❌ When I scan an invalid address QR code using the QR scanner on the send flow I should see the appropriate warning message: Wrong error message appears https://drive.google.com/file/d/1GaZPEBKgoV1MevkBepDbQ_-BVfFMvUXb/view
✅ A user can scan a private key QR code using the in-app camera to import an account: https://drive.google.com/file/d/1EvJD9SUT7xJrchvTiHs0aa3O6XMmRXiW/view
✅ User scans MMM Receive QR code on different network: ❗Chain ID 1 not found error when scanning Eth receive QR from another network https://drive.google.com/file/d/16riGqB1QWlGvgk2sk_6RwnLvSoy6FFvV/view
Setting: General view ✅ Scenario: Changing the device language from English to Russian: ❗ “Your wallet is ready” welcome screen is in English https://drive.google.com/file/d/1DNGFwYK0NR7N4t4G_I4FE7b0K_Ha6jSf/view
✅ Scenario: Changing the app language from English to Filipino: https://drive.google.com/file/d/1c8u08rqCzuNILTvzPu6bSAXQ569s4tmj/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: ✅ Scenario: Adding browser Favorites: ✅ Scenario: Browser Options Menu: Browser back button - Share, Network change in wallet, & New Tab - ✅ Scenario: Visiting a malicious website prompts the user with the phishing detection warning: ❌ Scenario: Navigate to opensea.io, rarible.com, pancakeswap.finance, app.uniswap.org, and connect wallet account ❗ Opensea.io connect redirects to app store to download MetaMask https://drive.google.com/file/d/1ERfHpJix2VqVODykyDTpk-tcz4PpkOoD/view OpenSea issue - https://drive.google.com/file/d/10kS5-PhYKudGcvs0UW7UK1_9an1DDq3g/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 Outline: 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/1iUN5PEbCR9kONyOfQJZNXRqafu951QG6/view
QA Sign-off for v7.23.0 build 1333
Bitrise
✅✅✅ pr_smoke_e2e_pipeline
passed on Bitrise! ✅✅✅
Commit hash: 80149e0974e6e45e669612c7d023420bd6eaa360 Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c430084c-bca9-48d5-8ea2-5af0300bfc06
[!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
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code