magento2
magento2 copied to clipboard
Fixed: Validation issue
Description (*)
Resolved Validation issue on Checkbox fields bundle products
Related Pull Requests
Fixed Issues (if relevant)
- Fixes magento/magento2#38229
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)
- [x] Pull request has a meaningful description of its purpose
- [x] All commits are accompanied by meaningful commit messages
- [x] 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)
Hi @aasim110. Thank you for your contribution! Here are some useful tips on 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
:exclamation: 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:
-
Database Compare
-
Functional Tests CE
-
Functional Tests EE
-
Functional Tests B2B
-
Integration Tests
-
Magento Health Index
-
Sample Data Tests CE
-
Sample Data Tests EE
-
Sample Data Tests B2B
-
Static Tests
-
Unit Tests
-
WebAPI Tests
-
Semantic Version Checker
You can find more information about the builds here :information_source: 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.
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run Functional Tests EE, Functional Tests CE, Functional Tests B2B
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
Hi @aasim110. Thanks a lot for your effort!
Could you please merge the latest changes from the 2.4-develop
branch to your own? Also, please check the failing functional tests. It looks like some assertions related to the bundle products in the shopping cart are failing at the moment.
Thank you!
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@rogyar seems like failed test not related to this commit, kindly check in detail
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run Functional Tests EE,Functional Tests CE,Functional Tests B2B
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run WebAPI Tests, Integration Tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@engcom-Hotel WebAPI Tests and Integration Tests succeed and functional tests are not related to the commit.
@aasim110 functional failure seems to be related to PR only. Please check below test at your end once all are related to bundle product.
- StorefrontEditBundleProductTest
- StorefrontBundlePlaceOrderWithMultipleOptionsSuccessTest
- StorefrontAssertFixedCartDiscountAmountForBundleProductTest
- StorefrontAddBundleOptionsToCartTest
here is the build report
Hi @aasim110.
As it was mentioned, the failing tests most likely related to the changes. For example, let's check the StorefrontAddBundleOptionsToCartTest
. As you can see from the report the system expects the displayed subtotal of the bundle product as 1,968.00
. After your change, the displayed subtotal is 492
. That's the reason why the tests are failing. A similar case is with other functional tests mentioned above.
Also, I see your point that the dependence between your chances and the cart page is not obvious, but there's a dependency. If some option wasn't checked on the product detail page, for example, it affects the subtotal in the cart of the added bundle. So, most likely, after your change, the added product is different (in terms of options).
You may think in the same way to resolve issues with other tests.
Hope it's helpful.
@aasim110 we are moving On Hold
this PR for now as PR need attention as per above comment
@aasim110 As the PR changes are causing build failure due to PR changes. Hence we are closing for now. Once you are ready to proceed please feel free to reopen the PR.