MetaMask / MetaMask/metamask-mobile
Remove Enzyme usage (2/5)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
### What is this about?
Replace enzyme usage in the follow files with React testing library
```
app/components/Approvals/AddChainApproval/AddChainApproval.test.tsx
app/components/Base/RemoteImage/index.test.tsx
app/components/Base/Keypad/Keypad.test.js
app/component-library/components-temp/CustomSpendCap/CustomSpendCap.test.tsx
app/components/UI/Transactions/index.test.tsx
app/components/UI/TransactionElement/index.test.tsx
app/components/UI/TokenImage/index.test.tsx
app/components/UI/StyledButton/index.test.tsx
app/components/UI/SkipAccountSecurityModal/index.test.tsx
app/components/UI/SettingsNotification/index.test.tsx
app/components/UI/NetworkInfo/index.test.tsx
app/components/UI/NavbarTitle/index.test.js
app/components/UI/LoginOptionsSwitch/LoginOptionsSwitch.test.tsx
app/components/UI/Identicon/index.test.tsx
app/components/UI/HintModal/index.test.tsx
app/components/UI/GenericButton/index.test.tsx
app/components/UI/EditGasFeeLegacy/index.test.tsx
app/components/UI/EditGasFee1559/index.test.tsx
app/components/UI/CollectibleOverview/index.test.tsx
app/components/UI/CollectibleContracts/index.test.tsx
```
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
- All files listed should no longer have traces of enzyme
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the listed test files and locating their Enzyme usage. Replace that usage with React Testing Library patterns while preserving the existing test intent, then run the affected tests and confirm all listed files contain no Enzyme traces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native, typescript
- Domain
- mobile-dev, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100