test: Refactor EditAccountNameView.js & EnableSecurityChecksView.js files to follow page object model

[SamuelSalas]

Description

We are aiming to refactor the page objects in the modal folder so that they strictly follow the page object model pattern. This would aide in providing more readable and help standardize the way we create our tests. Because of the amount of files remaining, this issue will focus on working on three files to refactor, as well as their respective testIDs.

Files inside the scope for this batch:

• EditAccountNameView.js
• EnableSecurityChecksView.js

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Regression test run: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c4b665ed-bfea-45b9-9f91-fb2c49c9a2c9

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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 63dd9be
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/da503418-222c-439f-aa35-3e2391190668

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

[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 SonarCloud