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

Added progress bar to multiple shipping address checkout #29045

Open
wants to merge 6 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

rav-redchamps
Copy link
Contributor

@rav-redchamps rav-redchamps commented Jul 8, 2020

Description (*)

Progress bar was missing on multiple shipping address checkout so added it.

After:

after-progress-bar

Before:

before-progress-bar

Related Pull Requests

None

Fixed Issues (if relevant)

None

Manual testing scenarios (*)

  1. Add any two products to the cart
  2. Use "Check Out with Multiple Addresses" option from cart

Questions or comments

None

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 Jul 8, 2020

Hi @rav-redchamps. 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.

@rav-redchamps
Copy link
Contributor Author

@magento run all tests

@rogyar
Copy link
Contributor

rogyar commented Jul 9, 2020

Hi @rav-redchamps. Could I kindly ask you to cover your changes with an MFTF test, please?
The main idea of the MFTF test is to go to the multishipping checkout and make sure that the progress bar is there.

Thank you!

@rogyar rogyar self-assigned this Jul 9, 2020
@rav-redchamps
Copy link
Contributor Author

@rogyar Sure will do.

Also, what about static test fail

https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/29045/a63931d14cac24ada97099d8ac3cd07e/Statics/allure-report-b2b/index.html#categories/a682a4a0a77e467c12b697f19023767c/7a090f189905edec/

with error

Layout file '/var/www/html/app/code/Magento/Multishipping/view/frontend/layout/multishipping_checkout.xml' uses following blocks that are not marked with @api annotation:
Magento\Multishipping\Block\Checkout\State

@rogyar
Copy link
Contributor

rogyar commented Jul 12, 2020

Hi @rav-redchamps. I believe you may skip it for now. Such decisions as marking classes as @api should be considered by Magento architects rather than during a refactoring. Thank you.

@sidolov sidolov added Priority: P3 May be fixed according to the position in the backlog. Risk: low Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Sep 8, 2020
Copy link
Contributor

@sidolov sidolov left a comment

Choose a reason for hiding this comment

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

@rav-redchamps changes look good to me! Please, cover changes with MFTF test and we will proceed with delivery

@engcom-Golf
Copy link
Contributor

Hi, @rav-redchamps!
Would you be able to proceed with covering changed logic with MFTF test?

@engcom-Golf engcom-Golf self-assigned this Sep 23, 2020
@rav-redchamps
Copy link
Contributor Author

Hi, @rav-redchamps!
Would you be able to proceed with covering changed logic with MFTF test?

Hi @engcom-Golf I want to, but not getting enough time these days. If someone else want to takeover & cover it with the test then please feel free to.

@engcom-Golf
Copy link
Contributor

engcom-Golf commented Sep 28, 2020

I will cover these PR changes with autotest.

@engcom-Golf
Copy link
Contributor

@magento run all tests

@engcom-Golf engcom-Golf force-pushed the multiple-shipping-address-progress-bar branch from 26b43a7 to 88b6e0e Compare September 29, 2020 08:27
@engcom-Golf
Copy link
Contributor

@magento run all tests

sidolov
sidolov previously approved these changes Sep 29, 2020
@ghost ghost removed the Progress: needs update label Sep 29, 2020
@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-8284 has been created to process this Pull Request
✳️ @sidolov, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Alfa engcom-Alfa self-assigned this Sep 30, 2020
@engcom-Alfa engcom-Alfa added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Sep 30, 2020
Copy link
Contributor

@engcom-Alfa engcom-Alfa left a comment

Choose a reason for hiding this comment

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

Hi @rav-redchamps .

During tesing, we faced the issue.

Problem: All messages appear above the progress bar

Manual testing scenario:

  1. Enable Table Rate shipping method;
  2. Go to Storefront;
  3. Add product to cart;
  4. Go to Shopping Cart;
  5. Go to Checkout with Multiple Addresses;
  6. Go to Shipping Information step;
  7. Click on the Continue to Billing Information button;

Actual Result: ✖️ Error message appears above the progress bar

2020-09-30_12-26

Expected Result: ✔️ On the Single Address checkout all messages appear under the progress bar

Screenshot from 2020-09-30 12-51-34

and another question is whether we need Order Success and Order Results steps if the order creation process ends at the Place Order step?
2020-09-30_13-29

@rav-redchamps Could you take a look?

Thanks!

@ghost ghost dismissed sidolov’s stale review September 30, 2020 10:36

Pull Request state was updated. Re-review required.

@engcom-Golf engcom-Golf removed their assignment Oct 2, 2020
@engcom-Hotel engcom-Hotel self-assigned this Oct 2, 2020
@engcom-Hotel
Copy link
Contributor

@magento run all tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Multishipping Priority: P3 May be fixed according to the position in the backlog. Progress: pending review Release Line: 2.4 Risk: low Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants