feat: 10550 Re-introduce test for measuring cold app start + JS bundle load time

[MarioAslau]

Description

Using react-native-performance as a performance measurement tool, which will be implemented here - #10521, we want to utilize E2E world for measuring cold app start + JS bundle load time.

Technical Details

• Add E2E test that measures The new App Start time in ColdStartToOnboardingScreen.feature replacing the old test
• Added a baseline measure to compare App Start time against.
  Values from 10 tests:
  //test 1: 383
  //test 2: 334
  //test 3: 380
  //test 4: 410
  //test 5: 394
  //test 6: 352
  //test 7: 602
  //test 8: 364
  //test 9: 359
  //test 10: 438
• E2E test check the performance numbers against the baseline value. If the new performance numbers is higher than the threshold, fail the test and vice versa

Related issues

Fixes:

Manual testing steps

1. Go to this page...

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

Commit hash: 9d50621
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5c2e723a-b6f1-4a15-bc3c-9e7e61aea5cd

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: 0415b27
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0caa17fd-5a2d-4dee-8924-bbcfb3e7b8f3

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: ab5b947
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b349b5ff-547a-49e6-b87d-d2aaf23a6cb7

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 1c5cdd3
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/aeaf8f7d-828a-4610-8001-0144592a6575

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
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
82.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[cortisiko]

🌮 🌮 🌮