Skip to content

chore(runway): cherry-pick test: update token used in ramps test (#14363)#14512

Merged
NicolasMassart merged 4 commits into
release/7.44.0from
runway-cherry-pick-7.44.0-1744125940
Apr 9, 2025
Merged

chore(runway): cherry-pick test: update token used in ramps test (#14363)#14512
NicolasMassart merged 4 commits into
release/7.44.0from
runway-cherry-pick-7.44.0-1744125940

Conversation

@runway-github

@runway-github runway-github Bot commented Apr 8, 2025

Copy link
Copy Markdown
Contributor

cherry-pick test: update token used in ramps test (#14363)

)

## **Description**

The token being used in a test was displaying an unexpected value in
different places and making the smoke fail, I updated the token used to
avoid this problem.

## **Related issues**

Fixes: failures in smoke 

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ✓ ] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ✓ ] 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](https://jsdoc.app/) format
if applicable
- [ ✓ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
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.
@runway-github runway-github Bot requested a review from a team as a code owner April 8, 2025 15:24
@metamaskbot metamaskbot added the team-runway-bot-deprecated DEPRECATED: please use "team-bots" instead label Apr 8, 2025
@github-actions

github-actions Bot commented Apr 8, 2025

Copy link
Copy Markdown
Contributor

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.

@NicolasMassart NicolasMassart left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me: this cherry pick matches the original PR.

@github-actions

github-actions Bot commented Apr 8, 2025

Copy link
Copy Markdown
Contributor

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: cb62dc6
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/80054cbc-fafd-4bd9-878b-a73d847a451d

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

@NicolasMassart NicolasMassart changed the title chore(runway): cherry-pick test: update token used in ramps test chore(runway): cherry-pick test: update token used in ramps test (#14363) Apr 9, 2025
@sonarqubecloud

sonarqubecloud Bot commented Apr 9, 2025

Copy link
Copy Markdown

@NicolasMassart NicolasMassart merged commit da1afa5 into release/7.44.0 Apr 9, 2025
@NicolasMassart NicolasMassart deleted the runway-cherry-pick-7.44.0-1744125940 branch April 9, 2025 10:44
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

team-runway-bot-deprecated DEPRECATED: please use "team-bots" instead

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants