chore: Enable e2e testing for flask builds in ci

[Andepande]

Description

Enable e2e testing on flask builds in ci to allow engineers and QA to run automated tests early in development, ensuring faster feedback and improved stability

Related issues

Fixes:
NA

Manual testing steps

1. Ensure the spec files are placed in the directory e2e/specs/flask, similar to the extension repo structure.

2. Navigate to Bitrise dashboard.

3. Start a new build for your project.

4. Select the branch you want to run the tests on.

5. In the build workflow, add or select the run_e2e_flask_pipeline step to trigger the E2E tests.

6. Wait for the build to complete and review the E2E test results.

7. If necessary, fix any issues identified during testing and rerun the pipeline.

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

• [z] 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: 62a1764
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9a04568b-167a-4c9f-88f0-a0cb26719c59

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.72%. Comparing base (687f60e) to head (62a1764).
Report is 30 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14283      +/-   ##
==========================================
+ Coverage   65.57%   65.72%   +0.14%     
==========================================
  Files        2218     2228      +10     
  Lines       47401    47434      +33     
  Branches     6663     6683      +20     
==========================================
+ Hits        31085    31176      +91     
+ Misses      14326    14263      -63     
- Partials     1990     1995       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: cdba09f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0a846e57-5e85-442b-b2f5-72a1e215d66f

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 SonarQube Cloud

[cortisiko]

🔥 🔥 🔥 🔥 🔥 🔥 🔥