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

Fix: add to cart grouped product when exists a sold out option #24955

Merged
merged 4 commits into from
Jan 17, 2020
Merged

Fix: add to cart grouped product when exists a sold out option #24955

merged 4 commits into from
Jan 17, 2020

Conversation

gihovani
Copy link
Contributor

@gihovani gihovani commented Oct 9, 2019

Description (*)

Fix to add to cart grouped product when exists a sold out option.

Fixed Issues (if relevant)

  1. [Grouped product] Can´t add simple products to cart if one other is out of stock #22304: [Grouped product] Can´t add simple products to cart if one other is out of stock

Manual testing scenarios (*)

  1. enable the option allow to show products without stock
  2. grouped product with more sub items
  3. at least one sub items have to be without stock (quantity=0)
  4. navigate to the PDS of the grouped product
  5. add at least on item of any available sub item
  6. add the item to the cart

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)

@gihovani gihovani requested a review from akaplya as a code owner October 9, 2019 21:59
@m2-assistant
Copy link

m2-assistant bot commented Oct 9, 2019

Hi @gihovani. 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.3-develop instance - deploy vanilla Magento instance

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

@gihovani
Copy link
Contributor Author

gihovani commented Oct 9, 2019

@magento give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @gihovani. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @gihovani, here is your Magento instance.
Admin access: https://i-24955-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@gihovani
Copy link
Contributor Author

gihovani commented Oct 9, 2019

Hi,

i tested it at 2.3-develop and it is reproducible.

Grouped Product

@osrecio osrecio self-assigned this Oct 10, 2019
Copy link
Member

@osrecio osrecio left a comment

Choose a reason for hiding this comment

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

I tested with vanila Magento and with your changes and works properly

@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

@gihovani thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@engcom-Bravo
Copy link
Contributor

✔️ QA passed

Copy link
Contributor

@VladimirZaets VladimirZaets left a comment

Choose a reason for hiding this comment

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

Hi @gihovani. Thanks for collaboration. Due to Magento Definition of Done all code must be covered by tests. Please cover your fix by automated tests.

@ghost ghost assigned VladimirZaets Oct 17, 2019
@VladimirZaets VladimirZaets added Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests and removed Progress: needs update labels Oct 17, 2019
@gihovani
Copy link
Contributor Author

gihovani commented Oct 25, 2019

Hi @gihovani. Thanks for collaboration. Due to Magento Definition of Done all code must be covered by tests. Please cover your fix by automated tests.

@VladimirZaets, I dont know, how can i create this test...
would you have a similar test for me to get inspired?

@sidolov sidolov changed the base branch from 2.3-develop to 2.4-develop December 5, 2019 17:19
@slavvka
Copy link
Member

slavvka commented Dec 9, 2019

@engcom-Foxtrot Could you please help @gihovani to cover the change with automated test?

@engcom-Golf engcom-Golf self-assigned this Jan 3, 2020
@engcom-Golf
Copy link
Contributor

I will take care of test coverage

@engcom-Golf engcom-Golf added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests and removed Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests labels Jan 3, 2020
@engcom-Golf
Copy link
Contributor

@VladimirZaets Well, case covered by unit test.

@engcom-Golf
Copy link
Contributor

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Jan 17, 2020

Hi @gihovani, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.