test: Move files to Network folder

[SamuelSalas]

Description

We currently have a few of our page object files lingering outside of a specific folder. As part of our ongoing efforts to improve the organization and maintainability of our test automation codebase, we need to move Page Object files into their respective folders. This will help streamline the project structure, making it easier for team members to locate and manage the files. The folder where each of the remaining files should be moved have to reflect the functionality or feature on the app. This same structure should be reflected on the selectors folder. First it would be required to create the Network folder

Files to relocate:

• e2e/pages/modals/NetworkAddedModal.js
• e2e/pages/modals/NetworkApprovalModal.js
• e2e/pages/modals/NetworkEducationModal.js
• e2e/pages/modals/NetworkListModal.js

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Regression test run: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9b76b659-e4e3-4882-af79-268c8b44878c?tab=workflows

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 failed on Bitrise! ❌❌❌

Commit hash: 3b24ab6
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/ce5cbf35-7f9e-4be6-b759-48b2718258bf

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: 7a43636
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f11bb275-edde-4adc-bae0-501d12fec311

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

Commit hash: a7cc1de
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e90826a3-c66f-4fbe-a943-e051cfdd1593

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