test(3615): E2E to check the labels displaying the default account and chai…

[EtherWizard33]

Description

E2E to assert the permission summary is displaying the expected content after the user has connected with default account and chain.

Related issues

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

Manual testing steps

1. yarn watch:clean
2. yarn test:e2e:ios:debug:build
3. yarn test:e2e:ios:debug:run <path to test file>

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 passed on Bitrise! ✅✅✅

Commit hash: 16569f7
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4019a4e6-5135-4393-99da-66b65fb1792c

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