test: add a new unit test to cover for multichain feature flags ON

[EtherWizard33]

Once we remove the feature flags, we can delete the old tests, until then this ensure both side of the code is tested.

Description

• Modifying the env variable corresponding to the feature flag didnt take effect in the test, had to find another way, mocking the getter of the feture flag
• Mocking the getter worked, but modifying the mock inside the same test file didnt take effect in the component, re-importing the component caused all other mocks to fail, setting all mocks a second time didn't work.
• Finally something did work, which is having each test in their own test file is the only way i could get the mocks initialized with expected values.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/3664

Manual testing steps

1. run npx jest app/components/Views/AccountPermissions/** and all tests should pass

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: 6f87244
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ce799e98-aa90-4e91-b4dd-3f56a0cbfefe

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

[tommasini]

Account permissions is a component that have some actions, we should aim to unit test those with react-testing-library

[EtherWizard33]

Account permissions is a component that have some actions, we should aim to unit test those with react-testing-library

agreed, thank you Tomas, this was just a first change to the tests of this component,
this week I have been focusing on e2e, and plan to be putting a lot more time on unit tests next week once e2e has more coverage :)

[sonarcloud]

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