-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Grouped product frontend quantity validation added and code refactor #39480
base: 2.4-develop
Are you sure you want to change the base?
Grouped product frontend quantity validation added and code refactor #39480
Conversation
Hi @Mohamed-Asar. Thank you for your contribution!
Allowed build names are:
You can find more information about the builds here For more details, review the Code Contributions documentation. |
@magento run all tests. |
Failed to run the builds. Please try to re-run them later. |
@magento run all tests |
…into bug/39479-grouped-product-qty-validation
…thub.com/Mohamed-Asar/magento2 into bug/39479-grouped-product-qty-validation
@magento run all tests |
…into bug/39479-grouped-product-qty-validation
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @Mohamed-Asar,
Thanks for updating the PR as per the review comment!
It seems some tests are still failing due to the changes. Please look into those.
Thanks
…into bug/39479-grouped-product-qty-validation
@magento run all tests |
@engcom-Hotel Do i need to add the dependency in composer.json for this modules( [Magento\InventoryConfigurationApi, Magento\InventorySalesApi]) ? and also these modules are not on this repo, so how can i proceed, do i need to mention in root composer.json and the module composer.json ? |
@magento run Static Tests |
Hello @Mohamed-Asar, I guess you need to mention the dependencies in the Thanks |
@engcom-Hotel i added before, static test failed due to composer dependency issue, please see this commit after that i removed. |
@Mohamed-Asar I suggest you to please go through with this documentation: https://developer.adobe.com/commerce/php/architecture/modules/dependencies/ I think we need to add them back. Thanks |
…into bug/39479-grouped-product-qty-validation
@magento run all tests |
@engcom-Hotel I’ve added the module dependency in the CatalogInventory module's composer.json, but the static tests are still failing. It seems we need to add the dependency in the root composer.json file. Would it be okay if I go ahead and add it there as well? Please let me know your suggestion. Also, I noticed that the following MFTF test is consistently failing. I reviewed the test case and found that it sets min_qty as 4, but tries to add only 1 quantity to the cart—expecting the product to be added successfully. However, in this PR, I’ve included min_qty validation, which is why the test is failing. Would it be okay if I update the test case accordingly? Thanks! |
Hello @Mohamed-Asar, Regarding the MFTF test failure, yes please update the test. As you resolved the bug related to validation which was not in place previously it might happen some existing tests fails. So generally we need to fix those. And regarding the composer dependency static test failure we will get back to you soon on this. Thanks |
@magento run all tests |
I fixed the mftf test case for min qty validation |
Description (*)
Grouped Product Frontend Quantity validation added
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
1.Create a Grouped Product and associate it with child products.
2. Set the following quantity properties for one of the child products:
- Minimum Qty Allowed in Shopping Cart: 2
- Maximum Qty Allowed in Shopping Cart: 10
- Qty Increments: 2
3.Open the Product Detail Page (PDP) of the Grouped Product and test invalid quantities for the selected child product (e.g., 1, 3, or 11) to confirm that invalid inputs are restricted.
Contribution checklist (*)