test: Add Stake e2e automation

[davibroc]

Description

These are the Stake flows this PR will automate:

• Stake
• Unstake
• Stake more
• Claim
• Making sure staking balance, banners, and actions are hidden for ETH assets that aren't on mainnet or holesky

To run them locally follow these steps:

• Build the app locally and make sure you set the following ENV variables:
  export MM_MULTICHAIN_V1_ENABLED="true"
export MM_CHAIN_PERMISSIONS="true"
export MM_PERMISSIONS_SETTINGS_V1_ENABLED="false"
export PORTFOLIO_VIEW="true"
export MM_SECURITY_ALERTS_API_ENABLED="true"
export MM_NETWORK_UI_REDESIGN_ENABLED= "false"

  and run yarn test:e2e:android:debug:build

• Run the following command yarn test:e2e:android:debug:run e2e/specs/stake/stake-action-smoke.spec.js

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: ae1c314
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/cd7cbe7b-104b-47cd-b67e-c2e84ca14a81

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: 696d3aa
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/16d880bd-4b7d-4a7e-a6f3-515eb0f28462

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: 3ad8b72
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7ebc9c24-78c2-4c2d-9ac9-3c95e6d5e448

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

[amitabh94]

Just a minor comment but overall LGTM!

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 33e519d
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fd48405e-2827-4796-95df-29996ca64c5d

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[amitabh94]

LGTM!

[chrisleewilcox]

LGTM