You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Whoops! Pull requests should be opened against develop, not main. Please reopen this PR against the correct branch.
🚫
A version label is required. A maintainer must add one.
🚫
No linked issue found. Please link a relevant open issue by adding the text "closes #<issue_number>" or "closes JIRA-<issue_number>" in your PR.
🚫
Missing information in PR. Please fill out the "Description" section.
Warnings
⚠️
Found the word "TODO" in the PR description. Just letting you know incase you forgot :)
Messages
📖
DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed).
📖
Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.
If your PR is missing information, check against the original template here. At a minimum you must have the section headers from the template and provide some information in each section.
Cypress tests in the following files did not pass 😔. All tests must pass before this PR can be merged
Verify content:
Error: Image size (1280x1869) different than saved snapshot size (1280x1463).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/aboutUsPage/aboutUsPage.spec.js/__diff_output__/AboutUs.diff.png
The response we received from your web server was:
502: Bad Gateway
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
verify google map api load with content:
Error: Image size (1280x11380) different than saved snapshot size (1280x10130).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/map.spec.js/diff_output/Page-Builder-Verify-Map---All-content.diff.png
verify mocked google map api with two markers and click event:
Error: Image size (1280x1580) different than saved snapshot size (1280x1404).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/map.spec.js/diff_output/Page-Builder-Verify-Map---2-Locations.diff.png
verify slider content:
Error: Image size (1280x1564) different than saved snapshot size (1280x1404).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page.diff.png
verify slider content 2:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: getCMSMockData. No request ever occurred.
Error: Image size (1280x1564) different than saved snapshot size (1280x1404).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-3.diff.png
verify slider content 4:
Error: Image size (1280x1564) different than saved snapshot size (1280x1404).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-4.diff.png
verify slider content 5:
Error: Image size (1280x1564) different than saved snapshot size (1280x1404).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-5.diff.png
verify slider content 6:
Error: Image size (1280x1564) different than saved snapshot size (1280x1404).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-6.diff.png
verify slider content 7:
Error: Image size (1280x5265) different than saved snapshot size (1280x4828).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-7.diff.png
verify slider content 8:
Error: Image size (1280x2755) different than saved snapshot size (1280x2678).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-8.diff.png
verify slider content 9:
Error: Image size (1280x5359) different than saved snapshot size (1280x5282).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-9.diff.png
verify slider content 10:
Error: Image size (1280x2749) different than saved snapshot size (1280x2380).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-10.diff.png
verify slider content 11:
Error: Image size (1280x6179) different than saved snapshot size (1280x5510).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-11.diff.png
verify slider content 12:
Error: Image size (1280x5234) different than saved snapshot size (1280x4398).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/slider.spec.js/diff_output/Page-Builder-Slider-Page-12.diff.png
The response we received from your web server was:
502: Bad Gateway
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
verify video content alignment:
Error: Image size (1280x4501) different than saved snapshot size (1280x4019).
See diff for details: /venia-integration-tests/src/snapshots/snapshotTests/pageBuilder/video.spec.js/diff_output/Page-Builder-Video-Alignment-Page.diff.png
user should be able to access the Categories via Home page and from Main Menu left drawer:
AssertionError: Timed out retrying after 30000ms: expected '[ <a.categoryLeaf-target-IF0.flex.flex-auto.justify-start.h-[3.5rem].items-center.-mx-5.px-sm.w-full>, 2 more... ]' to be 'visible'
This element [ <a.categoryLeaf-target-IF0.flex.flex-auto.justify-start.h-[3.5rem].items-center.-mx-5.px-sm.w-full>, 2 more... ] is not visible because its parent <aside.navigation-root_open-qjl.navigation-root-eCb.bg-white.bottom-0.grid.left-0.max-w-modal.opacity-0.overflow-hidden.fixed.top-0.w-full.z-menu.invisible.shadow-modal> has CSS property: visibility: hidden
user can edit account information with default badge position:
This element <button.linkButton-root-Bk1.clickable-root-3it.cursor-pointer.inline-flex.items-center.justify-center.leading-none.pointer-events-auto.text-center.font-semibold.max-w-full.text-brand-dark.underline.hover_text-colorDefault> is not visible because its parent <div.editForm-changePasswordButtonContainer-J0y.pt-xs> has CSS property: visibility: hidden
Fix this problem, or use {force: true} to disable error checking.
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetStoreConfigDataQuery. No request ever occurred.
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlSignInAfterCreateMutation. No request ever occurred.
user should be able to add and remove products from wishlist:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlSignInAfterCreateMutation. No request ever occurred.
user should be able to create a new account and edit their information:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlSignInAfterCreateMutation. No request ever occurred.
should display Default Store View and USD currency by default:
AssertionError: Timed out retrying after 30000ms: Expected to find element: [data-cy="Header-switchers"] [data-cy="StoreSwitcher-root"] [data-cy="StoreSwitcher-trigger"], but never found it.
should display EUR currency by default if French Store View is selected:
This element <button.switcherItem-root-zCT.flex.items-center.w-full> is not visible because its parent <li.storeSwitcher-menuItem-33L.hover_bg-subtle> has CSS property: visibility: hidden
Fix this problem, or use {force: true} to disable error checking.
This element <button.switcherItem-root-zCT.flex.items-center.w-full> is not visible because its parent <li.storeSwitcher-menuItem-33L.hover_bg-subtle> has CSS property: visibility: hidden
Fix this problem, or use {force: true} to disable error checking.
This element <button.switcherItem-root-zCT.flex.items-center.w-full> is not visible because its parent <li.storeSwitcher-menuItem-33L.hover_bg-subtle> has CSS property: visibility: hidden
Fix this problem, or use {force: true} to disable error checking.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
TODO: Describe your changes in detail here.
Related Issue
Closes #ISSUE_NUMBER.
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist