MetaMask / MetaMask/metamask-mobile
Add custom account name to upgrade tests
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### Describe the bug
In light of an RC issue discovered [here](https://github.com/MetaMask/metamask-mobile/issues/9988) we have the opportunity to update the upgrade tests to help ensure that a custom account name will persist through the update.
Will resolve [477](https://github.com/MetaMask/accounts-planning/issues/477)
### Expected behavior
Given the user enters a custom account name/label
When the user installs an app update
Then the custom account name/label persists
### Screenshots/Recordings
_No response_
### Steps to reproduce
1. configure wallet
2. enter custom name for an account
3. install app update
4. verify custom account name persists
### Error messages or log output
_No response_
### Detection stage
During release testing
### Version
7.24.1
### Build type
None
### Device
any
### Operating system
iOS, Android
### Additional context
_No response_
### Severity
_No response_
Contributor guide
Research direction
Start by locating the existing upgrade tests in the mobile project and review how they configure accounts and verify state after an app update. Add coverage for entering a custom account name or label before the update, then confirm the same name persists afterward on iOS and Android.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100