-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Fixed issue 25910 choose drop down not close when open another #26090
Fixed issue 25910 choose drop down not close when open another #26090
Conversation
Hi @Usik2203. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
Hi @Usik2203, thank you for your contribution! |
Hi @Usik2203, thank you for your contribution! |
Hi @Usik2203, thank you for your contribution! |
Hi @Usik2203, thank you for your contribution! |
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.
Hi @Usik2203. Thank you for the fix. According to the last updates to the definition of done all changes should be covered by automated tests. Could I kindly ask you to cover your changes by MFTF test?
Thank you.
Hi, @rogyar |
@magento give me test instance |
Hi @Usik2203. Thank you for your request. I'm working on Magento instance for you |
Hi @Usik2203, here is your new Magento instance. |
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.
Hi @Usik2203. Thank you for providing the test. The current version of the test emulates swatch clicking behavior. However, It does not perform any checks (assertions).
Your test should assert that after clicking on a new swatch the previous dropdown is not visible.
Pull Request state was updated. Re-review required.
Hi @rogyar |
Hi @rogyar, thank you for the review. |
✔️ QA passed |
Hi @Usik2203, thank you for your contribution! |
Description (*)
This PR fixed #25910: issue
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)