Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: Reverse TCP port for edit address test #13129

Merged
merged 1 commit into from
Jan 22, 2025
Merged

Conversation

cortisiko
Copy link
Member

Description

The edit address test is passing (not even sure how this is possible) and failing (as expected) on CI. In order to utilize fixtures, specifically for android, the emulator needs to be able to communicate with the fixture server. The test in question was missing the line of code to change ports.

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

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.

@cortisiko cortisiko added Run Smoke E2E Triggers smoke e2e on Bitrise area-qa Relating to QA work (Quality Assurance) labels Jan 22, 2025
@cortisiko cortisiko requested a review from a team as a code owner January 22, 2025 22:58
@metamaskbot metamaskbot added the team-qa QA team label Jan 22, 2025
Copy link
Contributor

github-actions bot commented Jan 22, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 7c4e00e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/839d51f1-73b9-43b3-af4d-3ab073261f38

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

@cortisiko cortisiko added the No QA Needed Apply this label when your PR does not need any QA effort. label Jan 22, 2025
Copy link
Contributor

@tommasini tommasini left a comment

Choose a reason for hiding this comment

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

Does this means that our UI is slower?

@cortisiko
Copy link
Member Author

@tommasini hmmm in this case it was test related. We forgot to reverse the port so that the test can utilize fixtures.

@cortisiko cortisiko added this pull request to the merge queue Jan 22, 2025
github-merge-queue bot pushed a commit that referenced this pull request Jan 22, 2025
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

The edit address test is passing (not even sure how this is possible)
and failing (as expected) on CI. In order to utilize fixtures,
specifically for android, the emulator needs to be able to communicate
with the fixture server. The test in question was missing the line of
code to change ports.

## **Related issues**

Fixes:

## **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.
@cortisiko cortisiko self-assigned this Jan 22, 2025
@cortisiko cortisiko removed this pull request from the merge queue due to a manual request Jan 22, 2025
@cortisiko cortisiko added this pull request to the merge queue Jan 22, 2025
Merged via the queue into main with commit 047f0f8 Jan 22, 2025
51 checks passed
@cortisiko cortisiko deleted the detox/fix-edit-address branch January 22, 2025 23:44
@github-actions github-actions bot locked and limited conversation to collaborators Jan 22, 2025
@metamaskbot metamaskbot added the release-7.40.0 Issue or pull request that will be included in release 7.40.0 label Jan 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-qa Relating to QA work (Quality Assurance) No QA Needed Apply this label when your PR does not need any QA effort. release-7.40.0 Issue or pull request that will be included in release 7.40.0 Run Smoke E2E Triggers smoke e2e on Bitrise team-qa QA team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants