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

Mntor-3130 - Verify that the Apps&Services header options work correctly. #4608

Closed
wants to merge 3 commits into from

Conversation

mozilloid
Copy link
Contributor

@mozilloid mozilloid commented May 30, 2024

References:

Jira: MNTOR-3130
Figma:

Description

Similarly to mntor-3131, goes to each option and verifies URL. For Apps&Services header, checks the URL based on a single RegExp.

Screenshot (if applicable)

Not applicable.

How to test

npx playwright test -g "Verify that the Apps and Services header options work correctly."

Checklist (Definition of Done)

  • Localization strings (if needed) have been added.
  • Commits in this PR are minimal and have descriptive commit messages.
  • I've added or updated the relevant sections in readme and/or code comments
  • I've added a unit test to test for potential regressions of this bug.
  • If this PR implements a feature flag or experimentation, the Ship Behind Feature Flag status in Jira has been set
  • Product Owner accepted the User Story (demo of functionality completed) or waived the privilege.
  • All acceptance criteria are met.
  • Jira ticket has been updated (if needed) to match changes made during the development process.
  • Jira ticket has been updated (if needed) with suggestions for QA when this PR is deployed to stage.

@mozilloid mozilloid self-assigned this May 30, 2024
Copy link

@mozilloid mozilloid marked this pull request as ready for review May 30, 2024 16:37
@mozilloid mozilloid requested a review from pdehaan May 30, 2024 16:37
src/e2e/pages/dashBoardPage.ts Outdated Show resolved Hide resolved
src/e2e/pages/dashBoardPage.ts Outdated Show resolved Hide resolved
src/e2e/pages/dashBoardPage.ts Outdated Show resolved Hide resolved
src/e2e/specs/dashboard.spec.ts Outdated Show resolved Hide resolved
src/e2e/specs/dashboard.spec.ts Outdated Show resolved Hide resolved
await clickOnLinkAndGoBack(
dashboardPage.servicesPocket,
/getpocket\.com|apps\.apple\.com|app\.adjust\.com/,
/.*(\/pocket-and-firefox\/?).*|.*about.*|.*pocket-stay-informed.*/,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Similarly here... it's getting a bit confusing since I'm trying to figure out which paths belong to which hosts between these two regexps. 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do you think there is a better way to do this if there are so many hosts and so many paths that are thus possible?

src/e2e/specs/dashboard.spec.ts Outdated Show resolved Hide resolved
);
await openProfileMenuItem(
dashboardPage.profileSettings,
/.*\/user\/settings.*/,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here re: https://monitor.mozilla.org/user/settings
I wonder if we could get the current project's baseURL and use await expect(page).toHaveURL(domainAndPath);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd still need to call .waitForURL() and pass in that URL. At that point, isn't it redundant?

src/e2e/utils/helpers.ts Outdated Show resolved Hide resolved
src/e2e/utils/helpers.ts Outdated Show resolved Hide resolved
@mozilloid mozilloid requested review from pdehaan and mansaj May 31, 2024 05:06
@mozilloid mozilloid closed this Jun 3, 2024
Copy link

github-actions bot commented Jun 3, 2024

Cleanup completed - database 'blurts-server-pr-4608' destroyed, cloud run service 'blurts-server-pr-4608' destroyed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants