test: add new unit tests after removing exclusions from Sonar config

[EtherWizard33]

Description

This PR contains the sonar coverage after removing exclusions for the sonar config file

Related issues

Contributes to: https://github.com/MetaMask/MetaMask-planning/issues/3663

Manual testing steps

run the unit tests using yarn test:unit

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

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.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: f4eab91
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a5526c28-39f2-4add-aed6-12f692d53272

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 16.66667% with 35 lines in your changes missing coverage. Please review.

Project coverage is 59.94%. Comparing base (faf5340) to head (c32d4a6).
Report is 14 commits behind head on main.

Files with missing lines	Patch %	Lines
...ts/Views/AccountPermissions/AccountPermissions.tsx	4.76%	19 Missing and 1 partial ⚠️
...nnectMultiSelector/AccountConnectMultiSelector.tsx	0.00%	5 Missing ⚠️
...ettings/PermissionsSettings/PermissionsManager.tsx	0.00%	3 Missing ⚠️
...rmissionsConnected/NetworkPermissionsConnected.tsx	33.33%	2 Missing ⚠️
...etworkVerificationInfo/NetworkVerificationInfo.tsx	50.00%	0 Missing and 1 partial ⚠️
...components/Views/AccountConnect/AccountConnect.tsx	0.00%	1 Missing ⚠️
...rmissionsConnected/AccountPermissionsConnected.tsx	0.00%	1 Missing ⚠️
app/components/Views/BrowserTab/index.js	0.00%	1 Missing ⚠️
app/components/Views/Settings/index.tsx	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #13031      +/-   ##
==========================================
+ Coverage   59.83%   59.94%   +0.10%     
==========================================
  Files        1873     1884      +11     
  Lines       42121    42202      +81     
  Branches     5473     5476       +3     
==========================================
+ Hits        25204    25298      +94     
+ Misses      15235    15213      -22     
- Partials     1682     1691       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: c32d4a6
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8344858a-1e98-421b-abbd-63b31d1bcabd

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 935f02c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/20f686cf-64a7-477e-bdfc-5bd6047dab7d

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud