Description

This PR is the beginning of a series aimed at reorganizing the test/e2e repository to create a structure that is both well-organized and easy to navigate. The goal is to enhance the overall efficiency and accessibility of our e2e tests. This reorganization work will be split into multiple PRs, ensures that each PR remains manageable and easy to review, facilitating better feedback and more efficient integration.

In this initial step, I've started by creating multiple folders within the test/e2e/tests repo to group tests by feature. This allows for a more intuitive organization, with each set of feature-related tests contained within its own dedicated folder. The tests that were most evidently associated with a specific feature have been sorted into the appropriate new folders. The remaining test cases, which may require further discussion or clarification to assign correctly, will be addressed in future PRs.

The reason behind organizing test cases by features is to streamline the ownership of tests, with each feature team being responsible for one or multiple folders related to the features they develop and maintain. This fosters a sense of ownership and aligns testing efforts closely with feature development. I did not create a separate repo for each feature team due to potential maintenance challenges, especially if we have team reorganizations in the future.

Additionally, other files such as helpers, modules, and utility files that support these tests are also planned to be reorganized in the following PRs.

Related issues

Fixes: #23296

Manual testing steps

Check if the organization is logical.

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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.