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

Resolved Issue #24785 #24800

Merged
merged 5 commits into from Oct 15, 2019
Merged

Conversation

drpayyne
Copy link
Contributor

@drpayyne drpayyne commented Oct 1, 2019

Description

Resolved issue #24785

Added a JS method to handle the state of checked links in a downloadable product. The state is now managed and reflected in the label. Also added MFTF test to test changing of label.

  • Unselect all is displayed only when all links are checked
  • Select all is displayed otherwise

Fixed Issues

  1. All selected values still display as Select all in downloadable product #24785: All selected values still display as Select all in downloadable product

Manual testing scenarios

  1. Create a downloadable product in admin with downloadable links which can be purchased separately
  2. Go to storefront, add the product to cart with both downloadable links checked
  3. Open minicart and edit the product just added
  4. Verify state of checked links with the conditions mentioned in the description

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)

@drpayyne drpayyne requested a review from DrewML as a code owner October 1, 2019 05:24
@m2-assistant
Copy link

m2-assistant bot commented Oct 1, 2019

Hi @drpayyne. 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.

@drpayyne
Copy link
Contributor Author

drpayyne commented Oct 1, 2019

@magento give me test instance

@magento-engcom-team
Copy link
Contributor

Hi @drpayyne. Thank you for your request. I'm working on Magento instance for you

@magento-engcom-team
Copy link
Contributor

Hi @drpayyne, here is your new Magento instance.
Admin access: https://pr-24800.instances.magento-community.engineering/admin
Login: admin Password: 123123q

@drpayyne drpayyne force-pushed the issue-24785 branch 5 times, most recently from 16239b6 to eaa54db Compare October 1, 2019 08:46
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 @dryadav. 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 1, 2019
@drpayyne
Copy link
Contributor Author

drpayyne commented Oct 1, 2019

@VladimirZaets Thank you. Although, I'm confused a bit. What test should I write? I have only added a method in a jQuery widget. 🤔

@VladimirZaets
Copy link
Contributor

@drpayyne I think in this case we can write a functional test and check what is displayed, or at least JS unit test, that will check the new method that you created.

If you need documentation how to do it, or some additional information feels free to ask.

@drpayyne
Copy link
Contributor Author

drpayyne commented Oct 1, 2019

@VladimirZaets yes, can I have some references or documentations? I've written only PHPUnit tests. Thanks a lot!

@sidolov
Copy link
Contributor

sidolov commented Oct 4, 2019

@drpayyne please, refer to Magento devdocs:
JavaScript unit testing with Jasmine
Introduction to the Magento Functional Testing Framework

@drpayyne
Copy link
Contributor Author

drpayyne commented Oct 6, 2019

@sidolov @VladimirZaets Hello, I added an MFTF test to test the changing of the label. Please review my code when you can. And thanks for helping me with the documentation reference.

Also, my Static Tests build is failing but says no errors in the Allure dashboard.

@ihor-sviziev ihor-sviziev removed their request for review October 6, 2019 08:42
@sidolov sidolov added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Oct 8, 2019
@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-6047 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Before:
before

After:
after

Changed let to var. 
Added 'use strict';
Remove empty line
magento-engcom-team pushed a commit that referenced this pull request Oct 15, 2019
@magento-engcom-team magento-engcom-team merged commit a2919d9 into magento:2.3-develop Oct 15, 2019
@m2-assistant
Copy link

m2-assistant bot commented Oct 15, 2019

Hi @drpayyne, 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.

@magento-engcom-team magento-engcom-team added this to the Release: 2.3.4 milestone Oct 15, 2019
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.

None yet

8 participants