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: Move files to the Browser folder #12034

Merged
merged 19 commits into from
Oct 29, 2024

Conversation

SamuelSalas
Copy link
Contributor

@SamuelSalas SamuelSalas commented Oct 25, 2024

Description

We currently have a few of our page object files lingering outside of a specific folder. As part of our ongoing efforts to improve the organization and maintainability of our test automation codebase, we need to move Page Object files into their respective folders. This will help streamline the project structure, making it easier for team members to locate and manage the files. The folder where each of the remaining files should be moved have to reflect the functionality or feature on the app. This same structure should be reflected on the selectors folder.

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Regression test run https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/46998a35-cba3-4462-a63d-398ababf4504?tab=workflows

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.

@SamuelSalas SamuelSalas added team-mobile-platform Run Smoke E2E Triggers smoke e2e on Bitrise Detox area-qa Relating to QA work (Quality Assurance) labels Oct 25, 2024
@SamuelSalas SamuelSalas self-assigned this Oct 25, 2024
@SamuelSalas SamuelSalas requested review from a team as code owners October 25, 2024 22:39
Copy link
Contributor

github-actions bot commented Oct 25, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 98aca2d
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3f293bf6-201f-4688-9a06-651cd67e25d7

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

@SamuelSalas SamuelSalas added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 26, 2024
Copy link
Contributor

github-actions bot commented Oct 26, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 696835c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9100ae90-24f2-48c4-b80a-08cc5522faac

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

@SamuelSalas SamuelSalas added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 28, 2024
Copy link
Contributor

github-actions bot commented Oct 28, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: ca3ceb6
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1a919d59-8c03-49ec-9209-0b4cdecb9a2b

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

@SamuelSalas SamuelSalas added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 28, 2024
Copy link
Contributor

github-actions bot commented Oct 28, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 233f8ab
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e5e38461-eb51-4129-96aa-e1e2d6869960

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

Copy link
Member

@cortisiko cortisiko left a comment

Choose a reason for hiding this comment

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

looks good, just a few comments

e2e/pages/Browser/BrowserView.js Show resolved Hide resolved
e2e/pages/Browser/AddBookmarkView.js Outdated Show resolved Hide resolved
@SamuelSalas SamuelSalas requested a review from cortisiko October 28, 2024 19:11
e2e/pages/Browser/ConnectedAccountsModal.js Show resolved Hide resolved
e2e/pages/Browser/ContractApprovalModal.js Outdated Show resolved Hide resolved
e2e/pages/Browser/SpamFilterModal.js Show resolved Hide resolved
e2e/pages/Browser/SigningModal.js Outdated Show resolved Hide resolved
e2e/pages/Browser/ConnectModal.js Outdated Show resolved Hide resolved
SamuelSalas and others added 4 commits October 28, 2024 13:45
<!--
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**

Feedback was received suggesting that the "swipe to swap" UI was often
navigating back instead of executing the swap. This PR replaces the
swipe with a button to address this issue and simplify the interaction.

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Related issues**

Fixes:

## **Manual testing steps**

1. Go to the swap page
2. Get quotes
3. See swap button

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

### **Before**
<img width="310" alt="Screenshot 2024-10-25 at 17 22 47"
src="https://github.com/user-attachments/assets/f93ba955-164e-4a6b-895b-400a56c8bda0">
<!-- [screenshots/recordings] -->

### **After**
<img width="309" alt="Screenshot 2024-10-25 at 17 24 04"
src="https://github.com/user-attachments/assets/3aacf0c1-1066-4dbd-ac62-bef8682c2660">
<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [x] 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).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] 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.
<!--
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.
-->

The Purpose of this task is to readd the portfolio connect e2e to the
regression tag.

Fixes:

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

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

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

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

- [ ] 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.

- [ ] 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.

Co-authored-by: Aslau Mario-Daniel <marioaslau@gmail.com>
@SamuelSalas SamuelSalas requested a review from a team as a code owner October 28, 2024 20:26
Copy link
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.

@SamuelSalas SamuelSalas added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 28, 2024
Copy link
Contributor

github-actions bot commented Oct 28, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 783a2f9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d3d73223-19a8-4b17-823a-bde8502280b6

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

@SamuelSalas SamuelSalas added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 28, 2024
Copy link
Contributor

github-actions bot commented Oct 28, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 75e7deb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9b0e32e2-432e-46de-9494-8748fc33cee9

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

@SamuelSalas SamuelSalas added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Oct 29, 2024
Copy link
Contributor

github-actions bot commented Oct 29, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 2769e0b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1b3d2ae0-1b44-44ce-a05e-d01cb09bb775

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

Copy link

@SamuelSalas SamuelSalas added this pull request to the merge queue Oct 29, 2024
Merged via the queue into main with commit 17aee21 Oct 29, 2024
43 checks passed
@SamuelSalas SamuelSalas deleted the tes/2000-e2e-move-files-to-browser-folder branch October 29, 2024 16:15
@github-actions github-actions bot locked and limited conversation to collaborators Oct 29, 2024
@metamaskbot metamaskbot added the release-7.35.0 Issue or pull request that will be included in release 7.35.0 label Oct 29, 2024
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) Detox release-7.35.0 Issue or pull request that will be included in release 7.35.0 Run Smoke E2E Triggers smoke e2e on Bitrise team-mobile-platform
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants