Skip to content

Grouped product frontend quantity validation added and code refactor #39480

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

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

Conversation

Mohamed-Asar
Copy link
Contributor

Description (*)

Grouped Product Frontend Quantity validation added

Related Pull Requests

Fixed Issues (if relevant)

  1. Grouped Product Frontend Quantity Validations are Missing #39479
  2. Magento 2.4.7 minAllowed missing product order qty  #39142

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 (*)

  • 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)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

Copy link

m2-assistant bot commented Dec 15, 2024

Hi @Mohamed-Asar. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ 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
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@m2-github-services m2-github-services added Partner: Ziffity partners-contribution Pull Request is created by Magento Partner labels Dec 15, 2024
@m2-community-project m2-community-project bot added Progress: pending review Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Dec 15, 2024
@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests.

Copy link

Failed to run the builds. Please try to re-run them later.

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

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

@engcom-Hotel
Copy link
Contributor

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

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

Hi @engcom-Hotel

I fixed the mftf test case for min qty validation

@engcom-Hotel
Copy link
Contributor

Hello @Mohamed-Asar,

Thanks for fixing the MFTF test, for the dependency failures, we are in discussion with the internal team. Hence moving it to On Hold bucket for now.

Thanks

@engcom-Hotel engcom-Hotel moved this from Changes Requested to On Hold in Community Dashboard Apr 14, 2025
@engcom-Hotel
Copy link
Contributor

Hello @Mohamed-Asar,

As per the internal discussion, we should not make the dependencies of the modules which are not part of the repo. So I think we can move to our previous approach ie Magento\CatalogInventory\Api\StockRegistryInterface.

So please do the needful and let us know whenever this PR is ready for review.

Thanks

@Mohamed-Asar
Copy link
Contributor Author

@magento run all tests

@Mohamed-Asar
Copy link
Contributor Author

@magento run Functional Tests B2B, Functional Tests CE, Integration Tests, Static Test

@Mohamed-Asar
Copy link
Contributor Author

@magento run Static Tests, Functional Tests B2B

@Mohamed-Asar
Copy link
Contributor Author

Hello @Mohamed-Asar,

As per the internal discussion, we should not make the dependencies of the modules which are not part of the repo. So I think we can move to our previous approach ie Magento\CatalogInventory\Api\StockRegistryInterface.

So please do the needful and let us know whenever this PR is ready for review.

Thanks

@engcom-Hotel I reverted the MSI Changes, please review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Partner: Ziffity partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: pending review Project: Community Picked PRs upvoted by the community
Projects
Status: Pending Review
Development

Successfully merging this pull request may close these issues.

5 participants