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

magento/magneto2#27570: fixed issue withsue with store id for cash on… #27582

Merged

Conversation

ledian-hymetllari
Copy link
Member

@ledian-hymetllari ledian-hymetllari commented Apr 4, 2020

Description (*)

Fixed the issue with store view for cash and delivery method

Fixed Issues (if relevant)

#27570

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)

@m2-assistant
Copy link

m2-assistant bot commented Apr 4, 2020

Hi @ledian-hymetllari. 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.4-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

@magento-engcom-team magento-engcom-team added Component: Sales Release Line: 2.4 Partner: Vaimo Pull Request is created by partner Vaimo partners-contribution Pull Request is created by Magento Partner Event: Global-Contribution-Day labels Apr 4, 2020
Copy link
Contributor

@nuzil nuzil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ledian-hymetllari

  1. Can you please check failed tests?
  2. Can you please cover this fix with additional test?

@ghost ghost added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Apr 29, 2020
@VladimirZaets
Copy link
Contributor

Hi @ledian-hymetllari. Thanks for collaboration. Due to Magento Definition of Done all code must be covered by tests. Please cover your fix by automated tests.

@VladimirZaets VladimirZaets self-assigned this May 1, 2020
@ledian-hymetllari
Copy link
Member Author

@VladimirZaets can you help me to fix these code tests please?

@VladimirZaets
Copy link
Contributor

@magento run all tests

@VladimirZaets
Copy link
Contributor

@ledian-hymetllari of course, I rerun tests to see what happens with them. What problem do you need?

@ledian-hymetllari
Copy link
Member Author

@VladimirZaets is taking a look into this, as this is not failing due to my changes.

@ledian-hymetllari
Copy link
Member Author

@VladimirZaets any info about this one please?

@magento-engcom-team
Copy link
Contributor

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

@engcom-Alfa
Copy link
Contributor

Hi @nuzil What is the current status of this PR?
Thanks!

@engcom-Alfa engcom-Alfa requested a review from nuzil July 23, 2020 09:09
@swnsma swnsma self-requested a review July 30, 2020 20:24
@magento-engcom-team
Copy link
Contributor

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

Copy link
Contributor

@nuzil nuzil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@swnsma thanks for catch it. Super strange that I do not getting any emails when new comments are appearing

@magento-engcom-team
Copy link
Contributor

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

@engcom-Alfa engcom-Alfa self-assigned this Aug 3, 2020
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Preconditions:

Magento multi-store setup (Main Website Store, Second Website Store)
'Cache on delivery' payment method is enabled

Manual testing scenario:

  1. Go to Admin->Stores -> Config -> Sales Methods -> Payment Methods -> Cache On Delivery and Change 'Cache on Delivery' method title in the scope of Second Website configurations;
    Screenshot from 2020-08-03 11-22-27

  2. Place the Order with 'cache on delivery' in the scope of Second Website Store.

Screenshot from 2020-08-03 11-24-25

  1. Open order details in Admin Panel

Before: ✖️ The Payment Method name is being used from Default Store scope

2020-08-03_11-27

After: ✔️ The Payment Method name is being used from Order Store scope

2020-08-03_11-33

@engcom-Charlie engcom-Charlie added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Aug 5, 2020
@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Aug 7, 2020
@magento-engcom-team magento-engcom-team merged commit 89318ba into magento:2.4-develop Aug 8, 2020
@m2-assistant
Copy link

m2-assistant bot commented Aug 8, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: test coverage Component: Sales Event: Global-Contribution-Day Partner: Vaimo Pull Request is created by partner Vaimo partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

8 participants