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

MC-36425: “Select Shipping Method” page of Multishipping Checkout is corrupted if a Customer use “go back” browser button to return to the page #31156

Closed
wants to merge 5 commits into from

Conversation

engcom-Kilo
Copy link
Contributor

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes “Select Shipping Method” page of Multishipping Checkout is corrupted if a Customer use “go back” browser button to return to the page #30268

Manual testing scenarios (*)

  1. see “Select Shipping Method” page of Multishipping Checkout is corrupted if a Customer use “go back” browser button to return to the page #30268

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Dec 3, 2020

Hi @engcom-Kilo. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Dec 3, 2020
…corrupted if a Customer use “go back” browser button to return to the page
<!--Clean up test data, revert configuration.-->
<deleteData createDataKey="product" stepKey="deleteProduct"/>
<deleteData createDataKey="customer" stepKey="deleteCustomer"/>
<magentoCLI command="config:set {{DisableFreeShippingMethod.path}} {{DisableFreeShippingMethod.value}}" stepKey="disableFreeShipping"/>
Copy link
Contributor

@rogyar rogyar Dec 4, 2020

Choose a reason for hiding this comment

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

That's so awesome that we don't clean cache anymore after setting a config via CLI anymore (it's invalidated automatically in this case).

Great job!

@rogyar rogyar added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Dec 4, 2020
@engcom-Kilo
Copy link
Contributor Author

@magento run all tests

<title value="Checkout with multiple addresses after returning on cart page during checkout."/>
<description value="Verify customer able to checkout with multiple addresses after returning to cart page and continue checkout with browser 'back' button."/>
<severity value="AVERAGE"/>
<testCaseId value="MC-39583"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add MC-39583 as has tests link to task
Please specify test Path in MC-39583 zephyr
Please add Expected result for steps in MC-39583 zephyr

</after>

<!--Add product to cart and proceed to multishipping checkout. -->
<actionGroup ref="LoginToStorefrontActionGroup" stepKey="loginToStorefrontAccount">
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add logout in after section but before customer delete


<!--Add product to cart and proceed to multishipping checkout. -->
<actionGroup ref="LoginToStorefrontActionGroup" stepKey="loginToStorefrontAccount">
<argument name="Customer" value="$$customer$$"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please dont use $$. Use single $ instead

@zakdma
Copy link
Contributor

zakdma commented Dec 7, 2020

@magento-engcom-team
Copy link
Contributor

@zakdma the branch with code successfully imported intomagento-tsg/magento2ce repository. Branch name: imported-magento-magento2-31156.

…corrupted if a Customer use “go back” browser button to return to the page
@zakdma
Copy link
Contributor

zakdma commented Dec 7, 2020

@magento run all tests

@zakdma zakdma self-requested a review December 7, 2020 13:58
@zakdma
Copy link
Contributor

zakdma commented Dec 7, 2020

@magento run all tests

@engcom-Bravo
Copy link
Contributor

engcom-Bravo commented Dec 7, 2020

✔️ QA Passed

Manual testing scenario

  1. Go to the Storefront as the created Customer
  2. Add the created Product (2pcs) to the Shopping Cart
  3. Open the mini-cart
  4. Click the {color:#0747a6}“View and Edit Cart”{color} link
  5. Click the “{color:#0747a6}Check Out with Multiple Addresses”{color} link
  6. Select shipping addresses
  7. Click the “Go to Shipping Information” button
  8. Select Flat Rate shipping method
  9. Click the “Continue to Billing Information” button
  10. Click the "Add or remove gift cards" link on the “Billing Information” page
  11. Wait until the “Shopping Cart” page is loaded completely
  12. Click the “go back” browser button (left arrow)
  13. Click the {color:#0747a6}”Back to Shipping Information” link on the “Billing Information” page

BEFORE applying changes provided in the PR, the web page was not fully loaded, and an Exception appeared
pr_before

AFTER switching to the PR, the page is fully loaded with no errors
pr_after2

The order can be placed successfully

@zakdma
Copy link
Contributor

zakdma commented Dec 7, 2020

@magento run Functional Tests EE, Integration Tests

@zakdma
Copy link
Contributor

zakdma commented Dec 7, 2020

@magento run Functional Tests B2B

@zakdma
Copy link
Contributor

zakdma commented Dec 8, 2020

@magento run Functional Tests B2B, Functional Tests EE, Integration Tests

@zakdma
Copy link
Contributor

zakdma commented Dec 8, 2020

@magento run Functional Tests B2B, Functional Tests EE

@zakdma
Copy link
Contributor

zakdma commented Dec 9, 2020

@magento-engcom-team
Copy link
Contributor

@zakdma the branch with code successfully imported intomagento-tsg/magento2ce repository. Branch name: imported-magento-magento2-31156.

@zakdma
Copy link
Contributor

zakdma commented Dec 9, 2020

@magento run all tests

@zakdma
Copy link
Contributor

zakdma commented Dec 9, 2020

@magento run Functional Tests CE

@zakdma
Copy link
Contributor

zakdma commented Dec 14, 2020

Changes was delivered in scope of internal ticket MC-36425

@zakdma zakdma closed this Dec 14, 2020
@m2-assistant
Copy link

m2-assistant bot commented Dec 14, 2020

Hi @engcom-Kilo, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Multishipping Priority: P2 A defect with this priority could have functionality issues which are not to expectations. QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
6 participants