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

Fixing bug with non-existent customer group breaking quote #28902

Conversation

kodubovik
Copy link
Contributor

@kodubovik kodubovik commented Jun 26, 2020

Description (*)

There's a bug when a customer group deleted, it's still referenced in active quotes which causes an error on the checkout page.
Such a quote becomes broken and the customer is not able to place an order. This pull request adds functionality for getting customer group from the current customer in case customer group saved to the quote does not exist.

Manual testing scenarios (*)

  1. Create a new customer group.
  2. Create a new customer. Link that customer to the customer group created on the previous step.
  3. Log in to the Magento storefront and add some products to the shopping cart.
  4. Go to the admin and delete the customer group created on step 1.
  5. Return to the storefront and proceed to checkout.
  • Expected result: a customer should be able to complete an order without any issue.
  • Actual result: an error "No such entity id = ... " displayed. Shipping methods are not rendered.
    missin_customer_group

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)

Resolved issues:

  1. resolves [Issue] Fixing bug with non-existent customer group breaking quote #29327: Fixing bug with non-existent customer group breaking quote

@m2-assistant
Copy link

m2-assistant bot commented Jun 26, 2020

Hi @kodubovik. 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.

@kodubovik
Copy link
Contributor Author

@magento run all tests

@swnsma swnsma self-requested a review June 26, 2020 15:36
@swnsma swnsma self-assigned this Jun 26, 2020
@swnsma swnsma added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 29, 2020
@swnsma
Copy link
Contributor

swnsma commented Jun 29, 2020

@magento run all tests

1 similar comment
@kodubovik
Copy link
Contributor Author

@magento run all tests

@swnsma
Copy link
Contributor

swnsma commented Jul 2, 2020

@magento run all tests

swnsma
swnsma previously approved these changes Jul 7, 2020
@swnsma swnsma added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage labels Jul 7, 2020
@magento-engcom-team
Copy link
Contributor

Hi @swnsma, thank you for the review.
ENGCOM-7793 has been created to process this Pull Request
✳️ @swnsma, 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

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 @kodubovik

Due to Magento Definition of Done all changes should be covered by automated tests.
Could you please cover your fix by a MFTF test?
Thank you.

@magento-engcom-team magento-engcom-team added partners-contribution Pull Request is created by Magento Partner Component: Checkout labels Jul 27, 2020
@magento-engcom-team
Copy link
Contributor

Hi @swnsma, thank you for the review.
ENGCOM-7793 has been created to process this Pull Request

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Manual testing scenario:

  1. Create a new customer group;
  2. Create a new customer. Link that customer to the customer group created on the previous step.
  3. Log in to the Magento storefront and add some products to the shopping cart.
  4. Go to the admin and delete the customer group created on step 1.
  5. Return to the storefront and proceed to checkout.

Before: ✖️ an error "No such entity id = ... " displayed. Shipping methods are not rendered.

Screenshot from 2020-07-28 10-49-13

After: ✔️ Shipping methods are rendered and the order was successfully created with the default customer group

Screenshot from 2020-07-28 11-18-33

@engcom-Charlie engcom-Charlie added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jul 29, 2020
@engcom-Alfa
Copy link
Contributor

@magento create issue

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Jul 31, 2020
@swnsma
Copy link
Contributor

swnsma commented Aug 2, 2020

@magento run all tests

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Aug 8, 2020

Hi @kodubovik, 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.

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 Award: bug fix Award: test coverage Component: Checkout Component: Quote Partner: Guidance Solutions partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: accept 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
Archived in project
Development

Successfully merging this pull request may close these issues.

[Issue] Fixing bug with non-existent customer group breaking quote
6 participants