Remove enzyme usage (4/5)

[Cal-L]

What is this about?

What is this about?

Replace enzyme usage in the follow files with React testing library

app/component-library/components/Form/TextFieldSearch/TextFieldSearch.test.tsx
app/component-library/components/Form/Label/Label.test.tsx
app/component-library/components/Form/HelpText/HelpText.test.tsx
app/component-library/components/Badges/BadgeWrapper/BadgeWrapper.test.tsx
app/component-library/components/Badges/Badge/Badge.test.tsx
app/component-library/components/Accordions/Accordion/Accordion.test.tsx
app/components/UI/TransactionElement/TransactionDetails/index.test.tsx
app/components/UI/Tabs/TabCountIcon/index.test.tsx
app/components/UI/Swaps/components/TokenSelectButton.test.js
app/components/UI/Swaps/components/TokenIcon.test.js
app/components/UI/PaymentRequest/AssetList/index.test.tsx
app/components/UI/LedgerModals/Steps/ErrorStep.test.tsx
app/components/UI/LedgerModals/Steps/ConfirmationStep.test.tsx
app/components/UI/AssetOverview/AssetActionButton/index.test.tsx
app/components/Views/confirmations/components/WatchAssetRequest/index.test.tsx
app/components/Views/confirmations/components/TypedSign/index.test.tsx
app/components/Views/confirmations/components/TransactionReview/index.test.tsx
app/components/Views/confirmations/components/SignatureRequest/index.test.tsx
app/components/Views/confirmations/components/PersonalSign/index.test.tsx
app/components/Views/confirmations/SendFlow/SendTo/SendTo.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